search

lwhay / asterixdb

Automatically exported from code.google.com/p/asterixdb
0 stars 0 forks source link

Managix: Incorrect evaluation of runtime information (process Ids) for an AsterixDB instance #764

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Subsequent to creation of an AsterixDB instance, Managix verifies if the CC and 
the NCs have come up on each machine in the cluster and records the process ids 
as meta information. An incorrect evaluation here makes Managix believe that 
the corresponding daemon is not up. Consequently the state of the AsterixDB 
instance is incorrectly evaluated as "unusable" though it is very much 
functional.

Original issue reported on code.google.com by RamanGro...@gmail.com on 27 Apr 2014 at 8:42

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
This bug is readily observable in the imaxon/vagrant-it branch (45c6f07b). It 
is reported that none of the CCs are up, but I can run queries regardless. It's 
hard to troubleshoot inside of the test itself, but bringing up the VMs 
manually and simply executing the commands that AsterixClusterLifeCycleIT does 
produces the exact same results.

Original comment by ima...@uci.edu on 12 May 2014 at 8:51