Hi, all,
I read the document about how to adding a new data center to existing clusters
posted at
http://www.datastax.com/documentation/cassandra/2.0/cassandra/operations/ops_add_dc_to_cluster_t.html
But I have a question: Are all those steps executed only at the new adding
cluster or on exist
>
> I did not check the code - is this snitch on by default and, maybe, used
> as wrapper for configured endpoint_snitch?
Yes, the dynamic snitch wraps whatever endpoint_snitch you configure, and
it's on by default.
> As I understand it, the dynamic snitch also has a default slight
> preference
On Thu, Nov 20, 2014 at 10:29 AM, Stephane Legay
wrote:
> How should I go about inspecting SSTables?
>
sstable2json (which comes with cassandra, generally, but is packaged
separately these days)
checksstablegarbage (from pythian tools, which might help you understand
how much redundant data you
Thanks for the response.
Yes, I went through 1.1, 1.2, 2.0 as rolling updates (entire cluster for
each minor version) and ran upgradesstables each time.
Yes, nodes are using the same tokens. I can see the tokens when running
nodetool ring. They're consistent with what we used to have.
Repairs were
On Thu, Nov 20, 2014 at 8:36 AM, Stephane Legay
wrote:
> I upgraded a 2 node cluster with RF = 2 from 1.0.9 to 2.0.11. I did
> rolling upgrades and upgradesstables after each upgrade.
>
To be clear, did you go through 1.1, and 1.2, or did you go directly from
1.0 to 2.0?
> We then moved our d
On Thu, Nov 20, 2014 at 9:03 AM, Tyler Hobbs wrote:
> The difference is likely due to the DynamicEndpointSnitch (aka dynamic
> snitch), which picks replicas to send messages to based on recently
> observed latency and self-reported load (accounting for compactions,
> repair, etc). If you want to
Hi Tyler,
thanks fort that hint. I think we may postpone the C* upgrade for now and will
give it another try with a higher version. There is no pressure on that.
Regards
Andi
From: Tyler Hobbs [mailto:ty...@datastax.com]
Sent: Thursday, November 20, 2014 6:09 PM
To: user@cassandra.apache.org
Su
Hmmm...I am using:
endpoint_snitch: com.datastax.bdp.snitch.DseDelegateSnitch
which is using:
delegated_snitch: org.apache.cassandra.locator.PropertyFileSnitch
(for this specific test cluster)
I did not check the code - is this snitch on by default and, maybe, used as
wrapper for configured en
This could be due to https://issues.apache.org/jira/browse/CASSANDRA-8239,
which is fixed in 2.1.2.
However, it sounds like the SSTables were present immediately after
upgrading, which would rule that out.
On Thu, Nov 20, 2014 at 10:25 AM, Andreas Finke
wrote:
> Hi Robert,
>
>
>
> thanks for y
The difference is likely due to the DynamicEndpointSnitch (aka dynamic
snitch), which picks replicas to send messages to based on recently
observed latency and self-reported load (accounting for compactions,
repair, etc). If you want to confirm this, you can disable the dynamic
snitch by adding th
>
> To be clear, I don't believe DSE is required to use OpsCenter. My
> understanding is that it can be used with vanilla Apache Cassandra, but I
> have never actually tried to do so.
Correct Rob, you can use Opscenter with vanilla Apache Cassandra.
Mark
On 20 November 2014 16:10, Robert Coli
I upgraded a 2 node cluster with RF = 2 from 1.0.9 to 2.0.11. I did
rolling upgrades and upgradesstables after each upgrade. We then moved our
data to new hardware by shutting down each node, moving data to new
machine, and starting up with auto_bootstrap = false.
When all was done I ran a repair
Hi Robert,
thanks for your fast reply. Luckily this was a upgrade in QA environment ;) We
are running SizeTierCompaction. I wonder whether all those files were created
during running sstables command. Unfortunately we didn’t check at that time.
I will try to reproduce again and if this is the
DSE can manage an existing cluster (even vanilla Cassandra). And you are
not required to use OpsCenter for DSE, of course.
As for the graphs...I do think that OpsCenter is not necessarily the ideal
graphing tool for Cassandra. If you want nice and detailed (and
independent) dashboards, you can fee
On Thu, Nov 20, 2014 at 7:00 AM, Andreas Finke
wrote:
> we upgraded a 6 node Cluster from Cassandra 2.0.7 to 2.1.1 recently
> sticking to this guide
>
> After upgrade cluster was less responsive than before. One node did not
> came up at all.
>
For the record :
https://engineering.eventbrite
On Thu, Nov 20, 2014 at 7:00 AM, Andreas Finke
wrote:
> we upgraded a 6 node Cluster from Cassandra 2.0.7 to 2.1.1 recently
> sticking to this guide:
>
>
>
>
> http://www.datastax.com/documentation/upgrade/doc/upgrade/cassandra/upgradeCassandraDetails.html
>
>
>
> After upgrade cluster was less
On Wed, Nov 19, 2014 at 7:20 PM, Clint Kelly wrote:
> We have DSE so I can use opscenter. I was just looking for something more
> precise than the graphs that I get from opscenter.
>
To be clear, I don't believe DSE is required to use OpsCenter. My
understanding is that it can be used with vani
ok thank you.
2014-11-20 16:02 GMT+01:00 Mark Reddy :
> Hi Adil,
>
> When using the default superuser ('cassandra') a consistency level of
> QUORUM is used. When using other users ONE is used.
>
> You are not supposed to use 'cassandra' user directly, except to create
> another superuser and use
Hi,
There is something odd I have observed when testing a configuration with
two DC for the first time. I wanted to do a simple functional test to prove
myself (and my pessimistic colleagues ;) ) that it works.
I have a test cluster of 6 nodes, 3 in each DC, and a keyspace that is
replicated as f
Hi Adil,
When using the default superuser ('cassandra') a consistency level of
QUORUM is used. When using other users ONE is used.
You are not supposed to use 'cassandra' user directly, except to create
another superuser and use that one from that point on.
Mark
On 20 November 2014 14:40, Adil
Hi,
we upgraded a 6 node Cluster from Cassandra 2.0.7 to 2.1.1 recently sticking to
this guide:
http://www.datastax.com/documentation/upgrade/doc/upgrade/cassandra/upgradeCassandraDetails.html
After upgrade cluster was less responsive than before. One node did not came up
at all. When checking
cassandra version 2.1.2
with the default user
we create another user and with this one we could login even if only one
node is up
2014-11-20 15:16 GMT+01:00 Mark Reddy :
> Hi Adil,
>
> What Cassandra version are you using? Are you using the default user or a
> non-default user?
>
>
> Mark
>
> On
Hi Adil,
What Cassandra version are you using? Are you using the default user or a
non-default user?
Mark
On 20 November 2014 08:20, Adil wrote:
> Hi,
> We have two data-center, we configured PasswordAuthenticator on each node,
> we increment the RF of system_auth to the number of nodes (each
Hello, have you try get statistics from jmx?
On Thu, Nov 20, 2014 at 10:55 AM, luolee.me wrote:
> Hi, everyone,
> I want to monitor the Cassandra cluster using Zabbix, but I have no idea
> about hot monitor the QPS on local Cassandra node ?
> I search the internet but haven't any result about ho
Hi,
We have two data-center, we configured PasswordAuthenticator on each node,
we increment the RF of system_auth to the number of nodes (each
data-center) as recommended.
We can logged-in via cqlsh without problem, but when i stop cassandra on
all nodes of a data-center we can't logged in in the o
25 matches
Mail list logo
