I do not think the feature is supposed to crash the server. It could be
that the message is the logs and the crash is not related to this message.
WARN might be a better logging level for any message, even though the first
threshold is WARN and the second is FAIL. ERROR is usually something more
dr
On Thu, Dec 26, 2013 at 3:03 PM, varun allampalli
wrote:
> I am trying to load using SSTableloader with cassandra 1.2 version like a
> million records. It streams very fast, but in the end its streaming gets
> stuck at two three machines in the cluster, rest all are 100% done.
>
The fragility of
Hi,
I am trying to load using SSTableloader with cassandra 1.2 version like a
million records. It streams very fast, but in the end its streaming gets
stuck at two three machines in the cluster, rest all are 100% done.
Has anybody seen such a problem and is there any tool I can use to diagnose
th
On Wed, Dec 25, 2013 at 11:29 AM, Andrey Razumovsky <
razumovsky.and...@gmail.com> wrote:
> OK, I figured that out - turns out that my sstables were in directory
> but not in /. Would be great to
> have a proper error message here..
I've opened a ticket to fix this:
https://issues.apache.org/j
Hello folks,
i have come up with a basic time series cql schema based on the articles
here:
http://www.datastax.com/dev/blog/advanced-time-series-with-cassandra
so simply put its something like:
rowkey, timestamp, col3, col4 etc...
where rowkey and timestamp are compound keys.
Where i am hav
