Sorry for the much delayed response. We had some issues with internal server errors at the time of your original posting, but the issues were resolved a short time afterward.
Atmos, being a distributed system, requires at least 2 nodes per RMG (an RMG is a collection of Atmos nodes in a given location). I believe that the system you had originally created consists of only a single node. As you power down and power back up that node, it's looking for the presence of other processes which it can't find and is therefore not initializing itself correctly.
The minimal tested configuration is 1 RMG consisting of 2 Atmos nodes. This configuration should provide you a more reliable experience in your test lab as well as allow you to distribute your REST requests across more than one Atmos node for greater availability.
rbala1
222 Posts
0
August 30th, 2010 07:00
Gonzalez,
Sorry for the much delayed response. We had some issues with internal server errors at the time of your original posting, but the issues were resolved a short time afterward.
Let us know if you still experience the problem.
Raj
David_Oswill
16 Posts
0
May 13th, 2011 12:00
Atmos, being a distributed system, requires at least 2 nodes per RMG (an RMG is a collection of Atmos nodes in a given location). I believe that the system you had originally created consists of only a single node. As you power down and power back up that node, it's looking for the presence of other processes which it can't find and is therefore not initializing itself correctly.
The minimal tested configuration is 1 RMG consisting of 2 Atmos nodes. This configuration should provide you a more reliable experience in your test lab as well as allow you to distribute your REST requests across more than one Atmos node for greater availability.