Yes, it was. I was dumping data from Oracle into Cassandra.
On Sun, Jul 4, 2010 at 11:11 AM, Andrew Rollins wrote:
> Is your IO under heavy load? If it is, that may be the cause, otherwise I'm
> not sure what causes significant lag. On Linux I like to use "iostat -tx 10"
> to check IO.
>
> - Andr
Is your IO under heavy load? If it is, that may be the cause, otherwise I'm
not sure what causes significant lag. On Linux I like to use "iostat -tx 10"
to check IO.
- Andrew
On Sun, Jul 4, 2010 at 4:04 AM, David Boxenhorn wrote:
> Thank you very much! I now understand things much better.
>
>
Thank you very much! I now understand things much better.
However, my configuration is as follows:
periodic
1
So I should see my commit log change after 10,000 milliseconds = 10 seconds?
It seems to take much longer to show up.
On Sun, Jul 4, 2010 at 10:52 AM, Andrew Rollins wrote:
> B
By default Cassandra syncs the commit log to disk periodically, so if you
are looking at file sizes, you won't see the most up to date numbers. This
is just like how if you tail a file that isn't flushing frequently, you
might wait a little while before you see the updates.
In periodic mode, Cassa
