Earlier today, a heap dump was generated on restbase1007.eqiad.wmnet, and the %p format specifier, which was supposed to be expanded to $PID... wasn't.
$ sudo ls -lh /var/lib/cassandra/ total 3.1G drwxr-x--- 2 cassandra cassandra 28K Oct 27 19:02 commitlog drwxr-x--- 161 cassandra cassandra 16K Oct 23 09:14 data -rw------- 1 cassandra cassandra 3.1G Oct 27 11:14 java_%p.hprof drwxr-x--- 2 cassandra cassandra 20K Oct 27 19:24 saved_caches
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| cassandra: fix HeapDumpPath and ErrorFile settings | operations/puppet | production | +2 -2 |
Change 249419 had a related patch set uploaded (by Filippo Giunchedi):
cassandra: fix HeapDumpPath and ErrorFile settings
Change 249419 merged by Filippo Giunchedi:
cassandra: fix HeapDumpPath and ErrorFile settings
completed, cassandra has been rolled restarted following openjdk security advisory
cassand+ 3001 457 35.5 42478052 23376880 ? SLl Dec02 13624:55 java -ea -javaagent:/usr/share/cassandra/lib/jamm-0.3.0.jar -XX:+CMSClassUnloadingEnabled -XX:+UseThreadPriorities -XX:ThreadPriorityPolicy=42 -Xms12g -Xmx12g -XX:+HeapDum OnOutOfMemoryError -XX:HeapDumpPath=/var/lib/cassandra/ -XX:ErrorFile=/var/lib/cassandra//hs_err_pid%p.log -Xss256k