Till Westmann has posted comments on this change. Change subject: This change fixes the sporadic connection refused errors after managix starts up an Asterix instance. This can mostly be seen during asterix-installer tests. The fix basically lets managix wait and listens through zookeeper for a signal from the cluster c ......................................................................
Patch Set 1: Ok, so the communication goes through Zookeeper and (in the current scenario) the Zookeeper instance is "owned" by Managix, right? And as you wrote earlier, the communication between the CC and Managix is initiated by Managix. So Managix should be able to tell the CC where it is when calling and so we wouldn't need to provide this information explicitly to the CC (introducing another configuration parameter). (Alternatively one could go to pull the information from the CC to avoid the additional parameter.) Also, it seems that we're introducing a dependency on the existence of a Zookeeper instance here. Is that correct? -- To view, visit https://asterix-gerrit.ics.uci.edu/365 To unsubscribe, visit https://asterix-gerrit.ics.uci.edu/settings Gerrit-MessageType: comment Gerrit-Change-Id: I0975308e1dc2650d8c2e50d58ff2c696b22eaaa4 Gerrit-PatchSet: 1 Gerrit-Project: hyracks Gerrit-Branch: master Gerrit-Owner: abdullah alamoudi <[email protected]> Gerrit-Reviewer: Chris Hillery <[email protected]> Gerrit-Reviewer: Ian Maxon <[email protected]> Gerrit-Reviewer: Jenkins <[email protected]> Gerrit-Reviewer: Murtadha Hubail <[email protected]> Gerrit-Reviewer: Till Westmann <[email protected]> Gerrit-Reviewer: abdullah alamoudi <[email protected]> Gerrit-HasComments: No
