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

fix: same NeonBee nodeId for multiple instances #161

Merged
merged 1 commit into from Aug 10, 2022
Merged

Conversation

halber
Copy link
Contributor

@halber halber commented Aug 4, 2022

The random NeonBee NODE_ID is the same for all NeonBee instances loaded
from the same classloader. This fix makes the NeonBee nodeId an instance
variable so that each NeonBee instance has its own nodeId.

The random NeonBee NODE_ID is the same for all NeonBee instances loaded
from the same classloader. This fix makes the NeonBee nodeId an instance
variable so that each NeonBee instance has its own nodeId.
@halber halber requested a review from a team as a code owner August 4, 2022 12:08
@s4heid
Copy link
Contributor

s4heid commented Aug 5, 2022

@halber I think this shouldn't be an issue, only if we would deploy multiple NeonBee instances on the same node... which should never be the case, right? Has this caused any problems in a scenario I am overlooking?

@halber
Copy link
Contributor Author

halber commented Aug 10, 2022

@halber I think this shouldn't be an issue, only if we would deploy multiple NeonBee instances on the same node... which should never be the case, right? Has this caused any problems in a scenario I am overlooking?

Right, it is unlikely that anyone would do this except for tests like io.neonbee.NeonBeeExtensionBasedTest#testNeonBeeWithClusters. In this case, you can't distinguish the instances by their IDs.

@halber halber merged commit 3b48202 into main Aug 10, 2022
@halber halber deleted the fix/staticNodeId branch August 10, 2022 15:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants