I have tried increasing timeout to 1 but no help. Also verified that
there is no network lost packets.
Jaydeep
On Wed, Mar 4, 2015 at 12:19 PM, Jan cne...@yahoo.com wrote:
HI Jaydeep;
- look at the i/o on all three nodes
- Increase the write_request_timeout_in_ms: 1
-
Hello Jaydeep;
Run cassandra-stress with R/W options enabled for about the same time and
check if you have dropped packets. It would eliminate the client as the source
of the error also give you a replicable tool to base subsequent tests/
findings.
Jan/
On Thursday, March 5, 2015
Thanks!
On Thu, Mar 5, 2015 at 11:10 AM, Aby Kuruvilla
aby.kuruvi...@envisagesystems.com wrote:
Thanks Yuki, have created a JIRA ticket
https://issues.apache.org/jira/browse/CASSANDRA-8924
On Thu, Mar 5, 2015 at 10:34 AM, Yuki Morishita mor.y...@gmail.com wrote:
Thanks.
It looks like a
Thanks Yuki, have created a JIRA ticket
https://issues.apache.org/jira/browse/CASSANDRA-8924
On Thu, Mar 5, 2015 at 10:34 AM, Yuki Morishita mor.y...@gmail.com wrote:
Thanks.
It looks like a bug. Can you create a ticket on JIRA?
https://issues.apache.org/jira/browse/CASSANDRA
On Thu, Mar
Hi Yuki
Thanks for the reply!
Here is the log from Cassandra server for the stream failure
INFO [STREAM-INIT-/192.168.56.1:58578] 2015-03-04 09:20:23,816
StreamResultFuture.java:109 - [Stream #98ba8730-c279-11e4-b8e9-55374d280508
ID#0] Creating new streaming plan for Bulk Load
INFO
Thanks.
It looks like a bug. Can you create a ticket on JIRA?
https://issues.apache.org/jira/browse/CASSANDRA
On Thu, Mar 5, 2015 at 7:56 AM, Aby Kuruvilla
aby.kuruvi...@envisagesystems.com wrote:
Hi Yuki
Thanks for the reply!
Here is the log from Cassandra server for the stream failure
On Wed, Mar 4, 2015 at 6:12 PM, Steffen Winther cassandra.u...@siimnet.dk
wrote:
Robert Coli rcoli at eventbrite.com writes:
1) stop node
2) move sstables from no-longer-data-directories into
still-data-directories
Okay, just into any other random data dir?
Few files here and there to
