Was this page helpful?
Caution
You're viewing documentation for a previous version. Switch to the latest stable version.
What to do if a Node Starts Automatically¶
If, for any reason, the Scylla service started before you had a chance to update the configuration file, some of the system tables may already reflect an incorrect status, and unfortunately, a simple restart will not fix the issue. In this case, the safest way is to stop the service, clean all of the data, and start the service again.
Procedure¶
- Stop the Scylla service. - sudo systemctl stop scylla-server - docker exec -it some-scylla supervisorctl stop scylla - (without stopping some-scylla container) 
- Delete the Data and Commitlog folders. - sudo rm -rf /var/lib/scylla/data sudo find /var/lib/scylla/commitlog -type f -delete sudo find /var/lib/scylla/hints -type f -delete sudo find /var/lib/scylla/view_hints -type f -delete 
- Start the Scylla service. - sudo systemctl start scylla-server - docker exec -it some-scylla supervisorctl start scylla - (with some-scylla container already running) 
- Run ‘nodetool status’ to verify all nodes are up and joined.