perfSONAR User Q&A and Other Discussion

[Hyojoon Kim <>]

Hi Andrew, 

Awesome! Thanks for these instructions: complete and easy to understand & follow :-) 

I guess I will go with the first method as we don’t have accumulated data just yet. But nonetheless, the second approach is great to know when that situation happens later or in another environment. 

Thanks,

Joon

On Aug 20, 2015, at 2:14 PM, Andrew Lake <> wrote:

Hi Joon,

What you need to do is change teh directory where cassandra and postgres store data. This is controlled through those respective tools configuration files and not esmond’s. You can find more information in the respective tools documentation but below should be the basic process:

- For cassandra, in /etc/cassandra/conf/cassandra.yaml change the commitlog_directory, data_file_directories and saved_caches_directory to the new locations you desire. Restart cassandra: /sbin/service cassandra restart

- For postgres, in /var/lib/pgsql/data/postgresql.conf change the data_directory to the new location. Restart postgres: /etc/init.d postgresql restart. You will need to rebuild the esmond tables after this change is made. To do so, follow the instructions here: http://software.es.net/esmond/rpm_install.html#configuration

An alternative way to do what you want is to stop both postgres and cassandra, move /var/lib/cassandra and /var/lib/pgsql to the new partition and then create symlinks to the new location in /var/lib/cassandra and /var/lib/pgsql. That saves the need to rebuild postgres and preserves any existing data.

Hope that helps,

Andy

On Thu, Aug 20, 2015 at 12:39 PM, Hyojoon Kim <> wrote:

Hello,

I have a measurement archive machine with esmond running, and there is a separate disk partition mounted on the machine where I want to store all the incoming measurement data from measurement points.

My question is: What is the proper way to change the default directory location for storing the measurement archive data?

Looking at "/opt/esmond.conf” without much knowledge is not helping that much, and the documentation online seems to mention multiple components related to storage (cassanda, tsrb, newdb, etc), so I’m not exactly sure what to touch.

I see there is a way to set the ESMOND_ROOT environment variable to a different one, but I am not sure if that is sufficient or not (or an overkill approach?). Seems not, actually.. I think I might have to create a new sql db in our desired directory and modify esmond.conf to point to that, but I am not sure if that is sufficient.

Any help or pointer would be great!

Thanks,
Joon