When priam restores when running as root, cleanDirectory changes the owner of the data dir to root about priam HOT 3 CLOSED

I don't see this being a bug with Priam. This is expected behavior in Linux environment. Because you ran tomcat as root, Priam's threads run with root privileges and the default umask on Linux systems is 022, so if you restore files, perhaps they will have root as the owner. IMHO running Tomcat or Cassandra as root is not recommended, I recommend configuring tomcat to run as cassandra user or giving it sudo rights to execute cassandra start/stop script.

from priam.

I agree this is expected behavior of the open system call. However if you are running as root, there should be a property indicating what the proper owner of the files should be.

IMHO running Tomcat or Cassandra as root is not recommended

Again, this is usually correct, but that's what the priam docs say. From https://github.com/Netflix/Priam/wiki/Setup:

Web Container setup

Since Priam changes the configuration files for Cassandra and starts/stops the services, the web container it's running in must either run as root, or it must have sufficient passwordless sudo rights to modify the cassandra.yaml file and execute the /etc/init.d/cassandra script.

There's a further lack of clarity here: note that sudo is not mentioned as the way of granting these rights - I would assume that the above should be read as granting execute rights on the script, and not granting sudo rights. What I recall from the code is that Priam actually does use sudo.

In any case, the overall point here is that if cassandra+tomcat can end up getting run as root, and if it is root, it should have a property, something like priam.cassandra_user which will default to "cassandra" that it will chown all files to.

from priam.

I've removed the confusing (if not slightly psychotic) advice to run as root, just need privs to execute rights on the script, as per pcn's recommendation. Thanks.

from priam.