Re: Getting ParNew GC in ... CMS Old Gen ... in logs

2015-04-22 Thread Phil Yang
Apr, 2015 at 11:41 pm *Subject*:Re: Getting ParNew GC in ... CMS Old Gen ... in logs I think this is just saying that young gen collection using Par new collector took 248 seconds. This is quite normal with CMS unless it happens too frequenltly several times in a sec. I think query time has

Re: Getting ParNew GC in ... CMS Old Gen ... in logs

2015-04-20 Thread Anuj Wadehra
I think this is just saying that young gen collection using Par new collector took 248 seconds. This is quite normal with CMS unless it happens too frequenltly several times in a sec. I think query time has more to do with read timeout in yaml. Try increasing it. If its a range query then

Getting ParNew GC in ... CMS Old Gen ... in logs

2015-04-20 Thread shahab
Hi, I am keep getting following line in the cassandra logs, apparently something related to Garbage Collection. And I guess this is one of the signs why i do not get any response (i get time-out) when I query large volume of data ?!!! ParNew GC in 248ms. CMS Old Gen: 453244264 - 570471312; Par

Re: Getting ParNew GC in ... CMS Old Gen ... in logs

2015-04-20 Thread Anuj Wadehra
I meant 248 milli seconds Sent from Yahoo Mail on Android From:Anuj Wadehra anujw_2...@yahoo.co.in Date:Mon, 20 Apr, 2015 at 11:41 pm Subject:Re: Getting ParNew GC in ... CMS Old Gen ... in logs I think this is just saying that young gen collection using Par new collector took 248 seconds