The stack won't help a ton since the memory leak will occur elsewhere… the stack will just have the point where the memory allocation failed :-(
On Mon, Jun 30, 2014 at 3:08 PM, Yuki Morishita <mor.y...@gmail.com> wrote: > Repair uses snapshot option by default since 2.0.2 (see NEWS.txt). > So you don't have to specify in your version. > > Do you have stacktrace when OOMed? > > On Mon, Jun 30, 2014 at 4:54 PM, Phil Burress <philburress...@gmail.com> > wrote: > > We are running into an issue with nodetool repair. One or more of our > nodes > > will die with OOM errors when running nodetool repair on a single node. > Was > > reading this http://www.datastax.com/dev/blog/advanced-repair-techniques > and > > it mentioned using the -snapshot option, however, that doesn't appear to > be > > an option in the version we have. We are running 2.0.7 with vnodes. Any > > insight into what might be causing these OOMs and/or what version this > > -snapshot option is available in? > > > > Thanks! > > > > Phil > > > > -- > Yuki Morishita > t:yukim (http://twitter.com/yukim) > -- Founder/CEO Spinn3r.com Location: *San Francisco, CA* blog: http://burtonator.wordpress.com … or check out my Google+ profile <https://plus.google.com/102718274791889610666/posts> <http://spinn3r.com>
