Thans Arun !
On Tue, Apr 28, 2015 at 9:44 AM, arun sirimalla wrote:
> Hi Neha,
>
>
> After you add the node to the cluster, run nodetool cleanup on all nodes.
> Next running repair on each node will replicate the data. Make sure you
> run the repair on one node at a time, because repair is an ex
Hi Neha,
After you add the node to the cluster, run nodetool cleanup on all nodes.
Next running repair on each node will replicate the data. Make sure you run
the repair on one node at a time, because repair is an expensive process
(Utilizes high CPU).
On Mon, Apr 27, 2015 at 8:36 PM, Neha Tr
Thanks Eric and Matt :) !!
Yes the purpose is to improve reliability.
Right now, from our driver we are querying using degradePolicy for
reliability.
*For changing the keyspace for RF=3, the procedure is as under:*
1. Add a new node to the cluster (new node is not in seed list)
2. ALTER KEYSPA
Hi,
Is there any minimum bandwidth requirement between two Geo Redundant
data centres?
What is the minimum latency that link between two Geo Redundant data
centres should have to get best efficient operations?
Regards,
Gaurav
Hello guys,
I have a cluster comprised of 2 nodes, configured with vnodes. Using
2.1.0-2 version of cassandra.
And I am facing an issue when I want to joing a new node to the cluster.
At first starting joining but then it got stuck:
UN 1x.x.x.x 348.11 GB 256 100.0%xx
Hi,
I would remove the node and start a new one. You can pick a specific
Cassandra release using user data (eg. --release 2.0.11)
Cheers,
Tommaso
On Mon, Apr 27, 2015 at 8:53 PM, Eduardo Cusa <
eduardo.c...@usmediaconsulting.com> wrote:
> Hi Guys, we start our cassandra cluster with the followi
Hi Guys, we start our cassandra cluster with the following ami :
ami-ada2b6c4
https://console.aws.amazon.com/ec2/home?region=us-east-1#LaunchInstanceWizard:ami=ami-ada2b6c4
Now we need to add a new node and we realize this ami has cassandra 2.1.4
intead of 2.1.0-2.
Is it safe to join this nod
Hi,
I am a newbie with Cassandra and thus need data modelling help as I haven't
found a resource that tackles the same problem.
The user case is similar to an email-system. I want to store a timeline of
all emails a user has received and then fetch them back with three
different ways:
1. All ema
On Sun, Apr 26, 2015 at 1:50 PM, Safa Topal wrote:
> We have a 3 node cluster with Cassandra 2.0.8 version. I am seeing data
> that should be dropped already. In JMX, I can see that
> DroppableTombstoneRatio is 0.68 for the column family and the
> tombstone_threshold was left as default for the C
Hi Neha,
I guess it depends why you are adding a new node – do you need more storage
capacity, do you want better resilience, or are you trying to increase
performance?
If you add a new node with the same amount of storage as the previous two,
but you increase the RF, you will use up all of t
It depends on why you're adding a new node. If you're running out of disk
space or IO capacity in your 2 node cluster, then changing RF to 3 will not
improve either condition - you'd still be writing all data to all three
nodes.
However if you're looking to improve reliability, a 2 node RF=2 clus
Hi
We have a 2 Cluster Node with RF=2. We are planing to add a new node.
Should we change RF to 3 in the schema?
OR Just added a new node with the same RF=2?
Any other Best Practice that we need to take care?
Thanks
regards
Neha
On 04/27/2015 08:18 AM, DE VITO Dominique wrote:
Just to know, is a OpsCenter future version, not relying on a mandatory
Thrift interface, on the road ?
Yes.
--
Kind regards,
Michael
Hi,
While reading the OpsCenter 5.1 docs, it looks like OpsCenter can't work if
Cassandra does not provide a Thrift interface (see [1] below).
Is it really the case ?
At first sight, it sounded weird to me, as CQL 3 is provided for months.
Just to know, is a OpsCenter future version, not relyi
No - it immediately removes the sstables on all nodes.
On Mon, Apr 27, 2015 at 7:53 AM, Ali Akhtar wrote:
> Wouldn't truncating the table create tombstones?
>
> On Mon, Apr 27, 2015 at 11:55 AM, Peer, Oded wrote:
>
>> I recommend truncating the table instead of dropping it since you don’t
>> n
Wouldn't truncating the table create tombstones?
On Mon, Apr 27, 2015 at 11:55 AM, Peer, Oded wrote:
> I recommend truncating the table instead of dropping it since you don’t
> need to re-issue DDL commands and put load on the system keyspace.
>
> Both DROP and TRUNCATE automatically create sna
16 matches
Mail list logo