Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Curator ( Zookeeper ) warning about Container nodes #2630

Open
cbeach47 opened this issue Dec 22, 2020 · 6 comments
Open

Curator ( Zookeeper ) warning about Container nodes #2630

cbeach47 opened this issue Dec 22, 2020 · 6 comments
Labels
Clustering Tech debt Anything to with the health of the code base

Comments

@cbeach47
Copy link
Contributor

cbeach47 commented Dec 22, 2020

Describe the bug
On start up in a cluster environment, curator logs the following warning in oEQ:

2020-12-22 20:38:31,910 [WARN] [app1] [Curator-PathChildrenCache-3:org.apache.curator.utils.ZKPaths.<clinit>()] - The version of ZooKeeper being used doesn't support Container nodes. CreateMode.PERSISTENT will be used instead.

To Reproduce

Steps to reproduce the behavior:

  1. Standard clustered env (2 oEQ (2020.1.6) nodes, 3 ZK (3.4.10) nodes)
  2. Start up ZK nodes
  3. Start up oEQ
  4. Note warning in oEQ log

Expected behavior

Possibly not to have the warning present OR an understanding that this is not an issue.

Platform:

  • OpenEquella Version: [at least 2020.1.6]
  • Zookeeper 3.4.10 (at least)
  • OS: [Linux]
  • Browser [Agnostic]

Additional context

  • The version of curator and zookeeper haven't changed from 2020.1.0 to 2020.1.6, so likely an issue for a while
  • The cpu / memory doesn't look to grow
  • The watches (via the 4LW wchc ) on zookeeper don't seem excessive
  • These folks are concerned about it - https://issues.apache.org/jira/browse/CURATOR-274
@cbeach47 cbeach47 changed the title Curator ( Zookeeper ) warning about P Curator ( Zookeeper ) warning about Container nodes Dec 22, 2020
@cbeach47
Copy link
Contributor Author

The curator link could be an older, resolved issue - oEQ uses curator 2.13.0.

@edalex-ian
Copy link
Member

Have you seen an issue/side effect from this though?

Personally I've not come across anything in our dev clusters, and haven't heard anything from our hosting team.

@stale
Copy link

stale bot commented Jun 2, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale Issue with low activity and flagged by Stale Bot label Jun 2, 2021
@edalex-ian edalex-ian removed the stale Issue with low activity and flagged by Stale Bot label Jun 2, 2021
@edalex-ian
Copy link
Member

We're hoping to revisit the upgrading of Apache Curator in 2022.1 so will look at this then as well.

@stale
Copy link

stale bot commented Oct 2, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale Issue with low activity and flagged by Stale Bot label Oct 2, 2021
@edalex-ian edalex-ian added the Tech debt Anything to with the health of the code base label Oct 3, 2021
@stale stale bot removed the stale Issue with low activity and flagged by Stale Bot label Oct 3, 2021
@edalex-ian
Copy link
Member

See also #114

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Clustering Tech debt Anything to with the health of the code base
Projects
None yet
Development

No branches or pull requests

2 participants