-
Notifications
You must be signed in to change notification settings - Fork 54
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
Dead Node #23
Comments
Questions
We have a unit tests which does this with 5 nodes so it would be interesting to understand if the same logic does with two nodes |
Currently, I applying gossip for Spring boot application. Each node is a instance of Spring Boot. Let's me some advice for apply gossip to Spring Boot Application. This is my configuration for Application 1 with port 8081. This is my configuration for Application 2 with port 8082. |
Each node needs an id. In your case you can generate a string or a uuid that will persist between restarts |
My application using Maybe it isn't generate id when use method |
Yes. This looks like a bug of that version. The id was not required in original versions but now it is. Can you please try trunk version. I will release the current trunk later today. |
I reviewed code. I think on StartupSetting class. |
RemoteGossipMember member = new RemoteGossipMember(memberJSON.getString("cluster"), This code is ok. We would not know the remote id until will connect to that host. Can you give a strip down example of your Spring boot example? |
When I use latest code. It's occur exception. I don't know why. Exception in thread "pool-6-thread-1" java.lang.NullPointerException This is my configuration for gossip |
This is my sample code. Please help me review code. |
This is a new piece of code. I will look at this. |
I found the bug you mentioned. The startup setting code was not setting the cluster name. I am looking at the unit test there because it is suspect. Sorry for the problems. Really cool app I want to take a deeper look at it. Please try the latest trunk again. SOrry for the issues, the cluster name is a new bit and I do not use the StartupSettings code path! |
I updated code it isn't occur Exeption. But when I start 2 instance of Spring Boot with port 8081 and 8082 corresponding to gossip.conf are:
We still don't know member node is UP. |
Great. Keep in mind the getMemberList does not include yourself, so in a two node cluster each node has me + getMemberList() = 1 |
What Do You Mean ? Am I implementing incorrect? So What I need to do to fix this? |
The only thing I am saying is. The member does not include the local member. The local member is assumed. |
Do you have any ideal for my application?. I don't know how to apply gossip to my application. How to a instance of spring boot know to other instance of spring boot. |
How do you start two compies of the application? mvn spring-boot:run -Drun.jvmArguments='-Dserver.port=8081' Whehn i do this they take the same config |
You need change port gossip.conf like port instance of Spring Boot. This is gossip.conf for port 8082: is it necessary run same gossip.conf? |
Hi,
I using this lib to intergrate in my application. I saw a issue. when I shutdown a node and turn on again, other node don't know this node.
Example: I have 2 node 1,2. First I open all node. Second I turn off node 2 then turn on again but Node 2 don't know node 1 is UP and node 1 also don't know node 2 is UP.
Please help me resolve this issue.
Thank for your support.
The text was updated successfully, but these errors were encountered: