You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by Ying Tang <iv...@gmail.com> on 2010/12/01 09:44:29 UTC
TheGC inspector's frequency
The GCInspector's start() method ,
In this method ,
StorageService.scheduledTasks.scheduleWithFixedDelay(t,
INTERVAL_IN_MS, INTERVAL_IN_MS, TimeUnit.MILLISECONDS);
t is Runnable t and it's run method is logIntervalGCStats.
According to this code segment , the logIntervalGCStats should be run
every second.
But the log of cassandra shows the logIntervalGCStats didn't run
every second,it's disorder .
How this happened?
--
Best regards,
Ivy Tang
Re: TheGC inspector's frequency
Posted by Jonathan Ellis <jb...@gmail.com>.
The key statement:
if (gcw.getDuration() > MIN_DURATION_TPSTATS)
{
logStats();
}
On Wed, Dec 1, 2010 at 2:44 AM, Ying Tang <iv...@gmail.com> wrote:
> The GCInspector's start() method ,
> In this method ,
> StorageService.scheduledTasks.scheduleWithFixedDelay(t,
> INTERVAL_IN_MS, INTERVAL_IN_MS, TimeUnit.MILLISECONDS);
> t is Runnable t and it's run method is logIntervalGCStats.
> According to this code segment , the logIntervalGCStats should be run
> every second.
> But the log of cassandra shows the logIntervalGCStats didn't run
> every second,it's disorder .
> How this happened?
>
> --
> Best regards,
>
> Ivy Tang
>
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of Riptano, the source for professional Cassandra support
http://riptano.com