Criteria followed by Managix in determining a conflict between multiple AsterixDB instances needs to be relaxed.

GoogleCodeExporter commented 9 years ago


Managix allows the end-user to create and manage multiple instances. Prior to 
creating an instance, the cluster configuration is compared with those of 
existing AsterixDB instances to detect any overlapping of physical machines. 
Managix considers an overlap as a conflict; a criterion that is too stringent. 
Overlapping is a conflict only if the conflicting instance is not in the 
INACTIVE state.

Relaxing the criterion would allow multiple AsterixDB instances running on 
overlapping nodes provided only
one of them is in the ACTIVE state at a given time.

Original issue reported on code.google.com by RamanGro...@gmail.com on 7 Feb 2014 at 4:18

GoogleCodeExporter commented 9 years ago

fixed in master

Original comment by RamanGro...@gmail.com on 7 Feb 2014 at 6:59

Changed state: Fixed

GoogleCodeExporter commented 9 years ago

Q: What's the reason for not allowing the same hardware to host multiple 
instances?  (Not as a best or even good practice, but if someone wanted to, why 
not?)

Original comment by dtab...@gmail.com on 7 Feb 2014 at 8:51

lwhay / asterixdb

Criteria followed by Managix in determining a conflict between multiple AsterixDB instances needs to be relaxed. #712