Gotta love, Eric!
http://www.slideshare.net/jericevans/nosql-yes-but-yescql-no
<https://twitter.com/#!/jericevans/status/78118651043127297>
--
SriSatish Ambati
Director of Engineering, DataStax
@srisatish
key lookups one by
> >>> one, while I really do not care about which key corresponds to which
> >>> result, a simple scraping of the underlying SSTable would
> >>> be perfect, because I could utilize the file cache coherency as I read
> >>> down the file.
> >>>
> >>>
> >>> Thanks
> >>> Yang
> >>>
> >>
> >>
> >>
> >> --
> >> Jonathan Ellis
> >> Project Chair, Apache Cassandra
> >> co-founder of DataStax, the source for professional Cassandra support
> >> http://www.datastax.com
> >>
> >
>
--
SriSatish Ambati
Director of Engineering, DataStax
@srisatish
Indeed. This is likely at the JVM level.. (if not lower down the stack)
Do you happen to have a hs*err file for the crash? Is it reproducible?
What 'java -version"? What version of linux?
thanks,
Sri
On Sun, Mar 20, 2011 at 5:48 PM, Jonathan Ellis wrote:
> segfaults are either a JVM bug (are y
Thanks, Dan:
Yes, -Xmn512MB/1G sizes the Young Generation explicitly and removes the
adaptive resizing out of the picture. (If at all possible send your gc log
over & we can analyze the promotion failure a little bit more finely.)
The low load implies that that you are able to use the parallel thr
Dan,
Please kindly attach your:
1) java -version
2) full commandline settings, heap sizes.
3) gc log from one of the nodes via:
-XX:+PrintTenuringDistribution \
-XX:+PrintGCDetails \
-XX:+PrintGCTimeStamps \
-Xloggc:/var/log/cassandra/gc.log \
4) number of cores on your system. How busy is the s
