cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] Commented: (CASSANDRA-1718) cassandra should chdir / when daemonizing
Date Wed, 12 Jan 2011 16:43:49 GMT


Jonathan Ellis commented on CASSANDRA-1718:

bq. Is there some way to tell the JVM to put its detritus elsewhere? lists -XX:HeapDumpPath
but nothing for a JVM crash log that I see.

> cassandra should chdir / when daemonizing
> -----------------------------------------
>                 Key: CASSANDRA-1718
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Packaging
>         Environment: Debian squeeze, Cassandra 0.7.0-beta3 and trunk (r1032649)
>            Reporter: paul cannon
>            Assignee: Eric Evans
>            Priority: Minor
>             Fix For: 0.7.1
>         Attachments: v1-0001-CASSANDRA-1718-switch-to-home-directory-on-startup.txt
> Common practice when daemonizing is to cd / to avoid pinning a filesystem.  For example,
if the oper happens to start Cassandra (by itself, or with a manual jsvc invocation, or with
the initscript) in /mnt/usb-storage, and there is something mounted there, then the oper will
not be able to unmount the usb device that was mounted at that location, since the cassandra
process has it open as its cwd.
> evidence that this isn't being done already:
> {noformat}
> ~% sudo lsof -p 9775 | awk '$4=="cwd"'
> jsvc    9775 cassandra  cwd    DIR                8,1     4096 147675 /home/paul/packages/cassandra/trunk
> {noformat}
> (That instance was invoked using the Debian initscript.)
> Obviously chdir("/") isn't necessary when not daemonizing, although it shouldn't hurt
> If there are concerns about Cassandra having an ongoing ability to open filenames relative
to its original working directory, then it should be sufficient just to do a "cd /" in the
initscript before starting Cassandra.  That case, at least, is particularly important.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message