Cassandra datastore should use the documented method to stop the cassandra service
Bug #1295362 reported by
Amrith Kumar
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack DBaaS (Trove) |
Fix Released
|
Medium
|
Amrith Kumar | ||
Bug Description
Currently the cassandra agent stops cassandra as:
STOP_CASSANDRA = "sudo killall java 2> /dev/null || true"
This is excessively harsh and doesn't give the service a chance to do any orderly shutdown.
The recommended way is:
sudo service cassandra stop
| Changed in trove: | |
| assignee: | nobody → Amrith (amrith) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to trove (master) | #1 |
| Changed in trove: | |
| status: | New → In Progress |
Revision history for this message
| Openstack Gerrit (openstack-gerrit) wrote Fix merged to trove (master) | #2 |
| Changed in trove: | |
| status: | In Progress → Fix Committed |
| Changed in trove: | |
| importance: | Undecided → Medium |
| milestone: | none → juno-1 |
| Changed in trove: | |
| status: | Fix Committed → Fix Released |
| Changed in trove: | |
| milestone: | juno-1 → 2014.2 |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/