NiFi cluster hostname #26
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
saidsef
force-pushed
the
cluster-node-names
branch
from
0318670
to
4c9bbfc
Compare
saidsef
force-pushed
the
cluster-node-names
branch
from
4c9bbfc
to
72ea6e7
Compare
saidsef
force-pushed
the
cluster-node-names
branch
from
72ea6e7
to
0500f6d
Compare
saidsef
force-pushed
the
cluster-node-names
branch
from
0500f6d
to
b465f89
Compare
saidsef
force-pushed
the
cluster-node-names
branch
from
b465f89
to
b9de228
Compare
saidsef
force-pushed
the
cluster-node-names
branch
from
b9de228
to
574a233
Compare
saidsef
force-pushed
the
cluster-node-names
branch
from
574a233
to
3bb548a
Compare
saidsef
force-pushed
the
cluster-node-names
branch
from
3bb548a
to
8c54395
Compare
saidsef
force-pushed
the
cluster-node-names
branch
from
8c54395
to
d010c0c
Compare
saidsef
force-pushed
the
cluster-node-names
branch
from
66a672c
to
b539c0c
Compare
saidsef
force-pushed
the
cluster-node-names
branch
from
b539c0c
to
d9f0fb5
Compare
saidsef
force-pushed
the
cluster-node-names
branch
from
d9f0fb5
to
377afce
Compare
saidsef
force-pushed
the
cluster-node-names
branch
from
377afce
to
e362aa0
Compare
saidsef
force-pushed
the
cluster-node-names
branch
from
e362aa0
to
dc49adb
Compare
saidsef
force-pushed
the
cluster-node-names
branch
from
dc49adb
to
4ee487f
Compare
saidsef
force-pushed
the
cluster-node-names
branch
from
4ee487f
to
e8b1ebd
Compare
saidsef
force-pushed
the
cluster-node-names
branch
from
e8b1ebd
to
ba01d78
Compare
saidsef
force-pushed
the
cluster-node-names
branch
from
ba01d78
to
d1b69ac
Compare
… with Kubernetes pod name from metadata name This StatefulSet of Apache NiFi deployment uses hostname as reference in the cluster names. When Apache NiFi nodes/pods occasionally terminated and redeployed old zombie nodes/pods hostnames are still list in the cluster page and can not be removed, this will/should fix that bug The HOSTNAME env variable is never empty as Kubernetes controller will always populate it if is not set The NIFI_CLUSTER_NODE_ADDRESS requires FQDN else it will generate it own address and that will result in error. Added setHostnameAsFQDN to Kubernetes StatefulSet deployment, this has been added as stable in Kubernetes 1.22 and we are currently running Kubernetes 1.27
saidsef
force-pushed
the
cluster-node-names
branch
from
d1b69ac
to
718d7ae
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This StatefulSet of Apache NiFi deployment uses hostname as reference in the cluster names. When Apache NiFi nodes/pods occasionally terminated and redeployed old zombie nodes/pods hostnames are still list in the cluster page and can not be removed, this will/should fix that bug