Cassandra can fail to come up

ckrintz / appscale

Automatically exported from code.google.com/p/appscale

0 stars 0 forks source link

Cassandra can fail to come up #128

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

In Eucalyptus and EC2, Cassandra does not run. This is because the uaserver
and pbserver pull in modules for all the databases, and the MongoDB module
we wrote tries to write a specific file on the filesystem (and fails to).

This failure causes the pbserver to fail altogether, but curiously only
occurs on Euca/EC2 and not Xen/KVM, or for any other database (including
MongoDB).

Will investigate, suspected fix is to change the Python egg directory to be
/tmp.

Original issue reported on code.google.com by shattere...@gmail.com on 9 Dec 2009 at 6:40

GoogleCodeExporter commented 9 years ago

Fix is implemented, will test in Euca tomorrow morning.

Original comment by shattere...@gmail.com on 10 Dec 2009 at 5:54

Changed state: Started

GoogleCodeExporter commented 9 years ago

Fixed, will be in AppScale 1.3 release.

Original comment by shattere...@gmail.com on 12 Dec 2009 at 1:24

Changed state: Fixed

GoogleCodeExporter commented 9 years ago

Post-mortem indicates that although the PYTHON_EGG environment variable was set 
in
~/.bashrc, it wasn't being picked up by the protocol buffer server, causing it 
to
revert to an incorrect value.

Setting the correct value for this variable in the AppController (who starts the
PBServer) allows the env var to be correct in the PBServer and allows for 
correct
execution.

Original comment by shattere...@gmail.com on 14 Dec 2009 at 7:13