Hi Sid,
I would recommend you to use either c3s or m3s instances for Opscenter and
for Cassandra nodes it depends on your use case.
You can go with either c3s or i2s for Cassandra nodes. But i would
recommend you to run performance tests before selecting the instance type.
If your use case require
Thanks good to know that.
On Tue, Jun 23, 2015 at 11:27 AM, Philip Thompson <
philip.thomp...@datastax.com> wrote:
> Yes, that is what he means. CL is for how many nodes need to respond, not
> agree.
>
> On Tue, Jun 23, 2015 at 2:26 PM, arun sirimalla
> wrote:
>
>>
ail if doesnt find data..
>>
>> Not convinced..
>>
>> Sent from Yahoo Mail on Android
>> <https://overview.mail.yahoo.com/mobile/?.src=Android>
>> --
>> *From*:"arun sirimalla"
>> *Date*:Tue, 23 Jun, 2015 at 11:
Scenario 1: Read query is fired for a key, data is found on one node and
not found on other two nodes who are responsible for the token
corresponding to key.
You read query will fail, as it expects to receive data from 2 nodes with
RF=3
Scenario 2: Read query is fired and all 3 replicas have dif
t.
>
> If it does a compaction, does it mean that it would also clean up my
> tombstone from my LeveledCompactionStrategy tables at the same time?
>
> Thanks for your help.
>
> On 19 Jun 2015, at 07:56 , arun sirimalla wrote:
>
> Hi Jean,
>
> Running nodetool repair
Hi Jean,
Running nodetool repair on a node will repair only that node in the
cluster. It is recommended to run nodetool repair on one node at a time.
Few things to keep in mind while running repair
1. Running repair will trigger compactions
2. Increase in CPU utilization.
Run node tool re
Hi Kaushal,
Here is the reference,
http://docs.datastax.com/en/cassandra/2.0/cassandra/architecture/architectureSnitchEC2_t.html
On Wed, May 27, 2015 at 9:31 AM, Kaushal Shriyan
wrote:
> Hi,
>
> Can somebody please share me details about setting up of EC2snitch in AWS
> single region which has
Analia,
Try running repair on node 3.
On Tue, May 12, 2015 at 7:39 AM, Analia Lorenzatto <
analialorenza...@gmail.com> wrote:
> Hello guys,
>
>
> I have a cluster 2.1.0-2 comprised of 3 nodes. The replication factor=2.
> We successfully added the third node last week. After that, We ran clean
Yes, Cassandra nodes accept writes during Repair. Also Repair triggers
compactions to remove any tombstones.
On Thu, May 7, 2015 at 9:31 AM, Khaja, Raziuddin (NIH/NLM/NCBI) [C] <
raziuddin.kh...@nih.gov> wrote:
> I was not able to find a conclusive answer to this question on the
> internet so I a
Hi Rahul,
If you are expecting 15 GB of data per day, here is the calculation.
1 Day = 15 GB, 1 Month = 450 GB, 1 Year = 5.4 TB, so your raw data size for
one year is 5.4 TB with replication factor of 3 it would be around 16.2 TB
of data for one year.
Taking compaction into consideration and you
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
I have a 6 (i2.2xlarge) node cluster on AWS with 4.5 DSE running on it. I
notice high compaction pending on one of the node around 35.
Compaction throughput set to 64 MB and flush writes to 4. Any suggestion is
much appreciated.
--
Arun
Senior Hadoop Engineer
Cloudwick
Champion of Big Data
http
12 matches
Mail list logo
