Hi all,
so after deep investigation, we found out that this is this problem
https://issues.apache.org/jira/browse/CASSANDRA-8058
Jiri Horky
On 10/20/2015 12:00 PM, Jiri Horky wrote:
> Hi all,
>
> we are experiencing a strange behavior when we are trying to bootstrap a
> new node. The problem
UNSUBSCRIBE
Forgot to mention I am using Cassandra 2.0.13
On Mon, Mar 23, 2015 at 5:59 PM, Anishek Agarwal anis...@gmail.com wrote:
Hello,
I am using a single node server class machine with 16 CPUs with 32GB RAM
with a single drive attached to it.
my table structure is as below
CREATE TABLE t1(id
My group is seeing the same thing and also can not figure out why its
happening.
On Mon, Mar 23, 2015 at 8:36 AM, Anishek Agarwal anis...@gmail.com wrote:
Forgot to mention I am using Cassandra 2.0.13
On Mon, Mar 23, 2015 at 5:59 PM, Anishek Agarwal anis...@gmail.com
wrote:
Hello,
I am
On Mon, Mar 23, 2015 at 7:27 AM, Brian Tarbox briantar...@gmail.com wrote:
My group is seeing the same thing and also can not figure out why its
happening.
On Mon, Mar 23, 2015 at 8:36 AM, Anishek Agarwal anis...@gmail.com
wrote:
Forgot to mention I am using Cassandra 2.0.13
This seems
I am using QUORUM
CQL
No SSDs (Anyway my IOPs is quite low so I dont think so it matters)
No compaction is running when I receive timeout
On Fri, Mar 6, 2015 at 12:35 AM, Carlos Rolo r...@pythian.com wrote:
What is the consistency level you are using?
Are you using Thrift or CQL?
Are you
What is the consistency level you are using?
Are you using Thrift or CQL?
Are you using SSDs?
Check if compactions are running when you get the timeouts.
Regards,
Carlos Juzarte Rolo
Cassandra Consultant
Pythian - Love your data
rolo@pythian | Twitter: cjrolo | Linkedin:
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
HI Jaydeep;
- look at the i/o on all three nodes
- Increase the write_request_timeout_in_ms: 1
- check the time-outs if any on the client inserting the Writes
- check the Network for dropped/lost packets
hope this helpsJan/
On Wednesday, March 4,
10 matches
Mail list logo