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

Passing user defined Node id through cmd #57

Open
nabhosal opened this issue Jul 20, 2017 · 5 comments
Open

Passing user defined Node id through cmd #57

nabhosal opened this issue Jul 20, 2017 · 5 comments

Comments

@nabhosal
Copy link

Hi,
We are deploying multiple vertx vertical using zookeeper cluster manager.... on zookeeper servers we need to track each vertical....but zookeeper assign some random UUID to each vertical. So mapping each vertical on zookeeper become difficult. It will be better if we can pass node id through cmd

@stream-iori
Copy link
Contributor

Does other vertx's cluster implementation provide such way? As i know the interface of vertx doesn't provide such method.
by the way you can get a verticle's deploymentID with callback handler in method vertx.deploy

vertx.deployVerticle("com.mycompany.MyOrderProcessorVerticle", res -> {
  if (res.succeeded()) {
   //get deploymentID
    System.out.println("Deployment id is: " + res.result());
  } else {
    System.out.println("Deployment failed!");
  }
});

@nabhosal
Copy link
Author

nabhosal commented Jul 21, 2017

Hazelcast shows membership info, so we don't need to track it through node id.... unfortunately zookeeper don't show such info.. only possible way is to track it on zookeeper server.
zookeeper don't use deployment id to map node id. So we don't know which deployment id map to corresponding zookeeper node id on zookeeper servers.

@takeseem
Copy link

my idea is #60

@nabhosal
Copy link
Author

I have fixes for above requirement, which we tested and deployed in our production setup...I would like to push those changes.... can someone help me on this...

@nabhosal
Copy link
Author

Copy pasted from issue 60
@stream1984 , We do agree its not a good idea to take nodeID from users. But, consider a deployment having a large number of service running then it becomes difficult for dev-ops to track which service is down even though we use zk watcher since UUID are non-intuitive.
We faced this issue in initial days, and we resolve by creating unique intuitive nodeIds.
Refer this fork, we are using this in our production
https://github.com/nabhosal/vertx-zookeeper

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants