Hi Steven,
One question, which is confusing , it's a server side issue or client side?
-Vivek
On Tue, Dec 24, 2013 at 12:30 PM, Vivek Mishra wrote:
> Hi Steven,
> Thanks for your reply. We are using version 1.2.9.
>
> -Vivek
>
>
> On Tue, Dec 24, 2013 at 12:27 PM, Steven A Robenalt > wrote:
Hi Steven,
Thanks for your reply. We are using version 1.2.9.
-Vivek
On Tue, Dec 24, 2013 at 12:27 PM, Steven A Robenalt
wrote:
> Hi Vivek,
>
> Which release are you using? We had an issue with 2.0.2 that was solved by
> a fix in 2.0.3.
>
>
> On Mon, Dec 23, 2013 at 10:47 PM, Vivek Mishra wrote
Hi Vivek,
Which release are you using? We had an issue with 2.0.2 that was solved by
a fix in 2.0.3.
On Mon, Dec 23, 2013 at 10:47 PM, Vivek Mishra wrote:
> Also to add. It works absolutely fine on single node.
>
> -Vivek
>
>
> On Tue, Dec 24, 2013 at 12:15 PM, Vivek Mishra wrote:
>
>> Hi,
>> I
Also to add. It works absolutely fine on single node.
-Vivek
On Tue, Dec 24, 2013 at 12:15 PM, Vivek Mishra wrote:
> Hi,
> I have a 6 node, 2DC cluster setup. I have configured consistency level to
> QUORUM. But very often i am getting "Broken pipe"
> com.impetus.client.cassandra.CassandraClie
Hi,
I have a 6 node, 2DC cluster setup. I have configured consistency level to
QUORUM. But very often i am getting "Broken pipe"
com.impetus.client.cassandra.CassandraClientBase
(CassandraClientBase.java:1926) - Error while executing native CQL
query Caused by: .
org.apache.thrift.transport.TTrans
> I assume you mean "seed_provider" setting in cassandra.yaml by "seed list".
> The current setting for vm1-vm6 is:
the value of seeds, e.g.
seed_provider:
- class_name: org.apache.cassandra.locator.SimpleSeedProvider
parameters:
- seeds: “127.0.0.1"
> seed_provider = vm1,vm
If this is still a concern can you post the output from nodetool gossipinfo ?
It will give the details of the nodes think of the other ones.
A
-
Aaron Morton
New Zealand
@aaronmorton
Co-Founder & Principal Consultant
Apache Cassandra Consulting
http://www.thelastpickle.com
On
Some background….
http://www.datastax.com/dev/blog/lightweight-transactions-in-cassandra-2-0
You can also get a timeout during the prepare phase, well anytime you are
waiting on other node really. The WriteTimeoutException returned from the
server includes a writeType
(https://github.com/apach
Hey Aaron,
Thanks for following up on this one.
I guess you're right and in any case, you're unlikely to want two
different versions of the code running at the same time.
Cheers,
Ben
On Mon, Dec 23, 2013 at 5:42 PM, Aaron Morton wrote:
> It depends a little on the nature of the change, but yo
> But in some cases, from one certain node, I get an WriteTimeoutException for
> a few minutes until an UnavailableException. It's like the coordinator don't
> know the status of the cluster. Any clue why is this happening?
Depending on how the node goes down there can be a delay in other nodes k
> Is there something wrong with it? Here 1234555665_53323232 and
> 2344555665_53323232 are super columns. Also, If I have to represent this data
> with new composite comparator, How will I accomplish that?
>
>
Composite types via pycassa
http://pycassa.github.io/pycassa/assorted/composite_typ
> First approach:
Sounds good.
> Second approach ( I used in production ):
If the row gets big enough this will have bad performance.
A
-
Aaron Morton
New Zealand
@aaronmorton
Co-Founder & Principal Consultant
Apache Cassandra Consulting
http://www.thelastpickle.com
On 19/12
AFAIK it mean the response from the server is for a different request, probably
something going wrong with the threading or trying to do async IO with thrift.
> I know it is ancient cassandra but just wanna learn it.
Looking at anything other than 2.0 will be wasting your time.
Cheers
---
nodetool proxyhistograms shows the throughput for the node, nodetool
cfhistograms shows it for a single node.
If you want to get an overview install something like Ops Centre
http://www.datastax.com/what-we-offer/products-services/datastax-opscenter
Cheers
-
Aaron Morton
New Z
> Cassandra version is : apache-cassandra-1.2.4
The latest 1.2 version is 1.2.13, you really should be on that.
> commitlog_total_space_in_mb: 16
> commitlog_segment_size_in_mb: 16
Reducing the total commit log size to 16 MB is a very bad idea, you should
return it to 4096 and the segment size
It depends a little on the nature of the change, but you need some coordination
between the schema change and your code. e.g. add new column, change code to
write to it or add new column, change code to use new column and not old
column, remove old column.
Cheers
-
Aaron Morto
mmm, my bad there.
First schema changes are always flushed to disk, so the commit log is not
really an issue.
Second when the commit log replays it just processes the mutations, the "Drop
keyspace” message comes from MigrationManager.announceKeyspaceDrop() and is not
called.
If you can rep
Interesting you even dare to do a live migration :-)
Do you do all Murmur-writes with the timestamp from the "Random"-data? So
that all migrated data is written with timestamps from the past.
On Mon, Dec 23, 2013 at 3:59 PM, Rahul Menon wrote:
> Christian,
>
> I have been planning to migrate
Christian,
I have been planning to migrate my cluster from random to murmur3 in a
similar manner. I intend to use pycassa to read and then write to the newer
cluster. My only concern would be ensuring the consistency of already
migrated data as the cluster ( with random ) would be constantly servi
Hi list,
has anyone ever tried to migrate a cluster from Random to Murmur?
We would like to do so, to have a more standardized setup. I wrote a small
(yet untested) utility, which should be able to read SSTable files from
disk and write them into a cassandra cluster using Hector. This migration
w
20 matches
Mail list logo
