perfSONAR User Q&A and Other Discussion

[Andrew Lake <>]

Hi Casey,

Sorry, I am still catching-up from being gone. If you want to just get rid of the cassandra data you can do the following (assuming centos 6):

/etc/init.d/cassandra stop

rm -rf /var/lib/cassandra/data/esmond

/etc/init.d/cassandra start

/etc/init.d/httpd24-httpd restart

Alternatively, if you have another volume with more space, you can just move the contents /var/lib/cassandra/ to the new volume and then replace /var/lib/cassandra/ with a  symlink to the new location. Cassandra won’t know the difference, we did that on a few esnet hosts awhile back that had a similar issue and it worked fine.

Thanks,

Andy

On January 3, 2018 at 12:57:57 PM, Casey Russell () wrote:

Group,

     Alright,  hearing no takers, It's a format and reinstall then.  This time with a better disk volume layout.

Sincerely,

Casey Russell

Network Engineer

785-856-9809

2029 Becker Drive, Suite 282
Lawrence, Kansas 66047

On Thu, Dec 28, 2017 at 11:28 AM, Casey Russell <> wrote:

A couple of us (maybe a few)  have posted in the last several months with problems where we've had a local archive grow beyond the space allowed on the local disk/volume.  Sometimes it's because of compaction issues, sometimes we just planned space poorly.  I've seen a script for selectively cleaning out just very specific entries from the esmond database.  

Has anyone worked out a procedure for just nuking the local esmond database information (*ideally just testing info, not the ip authorization / password information) and starting over with an empty database?

 

Sincerely,

Casey Russell

Network Engineer

785-856-9809

2029 Becker Drive, Suite 282
Lawrence, Kansas 66047