Thank You,
Regards,
Srini
Hey All,
Any info on this topic.?
Thank You,
Regards,
Srini
On Wed, Aug 8, 2018, 9:46 PM srinivasarao daruna
wrote:
> Hi All,
>
> We have built Cassandra on AWS EC2 instances. Initially when creating
> cluster we have not considered multi-region deployment and we have used AWS
Hi All,
We have built Cassandra on AWS EC2 instances. Initially when creating
cluster we have not considered multi-region deployment and we have used AWS
EC2Snitch.
We have used EBS Volumes to save our data and each of those disks were
filled around 350G.
We want to extend it to Multi Region and
Hi,
Recently one of our spark job had missed cassandra consistency property and
number of concurrent writes property.
Due to that, some of mutations are failed when we checked tpstats. Also, we
observed readtimeouts are occurring with not only the table that the job
inserts, but also from other
nathan Haddad <j...@jonhaddad.com> wrote:
Did you create the nodes with the same tokens?
On Sat, May 13, 2017 at 8:44 AM srinivasarao daruna <sree.srin...@gmail.com>
wrote:
> Hi,
>
> We have a cassandra cluster built on Apache Cassandra 3.9 with 6 nodes and
> RF = 3
Hi,
We have a cassandra cluster built on Apache Cassandra 3.9 with 6 nodes and
RF = 3. As part of re-building the cluster, we are testing the backup and
restore strategy.
We took the snapshot and uploaded the files to S3 and data has been saved
the data with folder names (backup_folder1 - 6 for
Hi,
We have a cassandra cluster built on Apache Cassandra 3.9 with 6 nodes and
RF = 3. As part of re-building the cluster, we are testing the backup and
restore strategy.
We took the snapshot and uploaded the files to S3 and data has been saved
the data with folder names (backup_folder1 - 6 for
> sent from my mobile
> Daemeon Reiydelle
> skype daemeon.c.m.reiydelle
> USA 415.501.0198
>
> On Mar 16, 2017 3:25 PM, "srinivasarao daruna" <sree.srin...@gmail.com>
> wrote:
>
>> Hi reiydelle,
>>
>> I cannot confirm the range as the volume
gt; arvydas.jonuso...@gmail.com> wrote:
>>
>>> If the data was written at ONE, consistency is not guaranteed. ..but
>>> considering you just restored the cluster, there's a good chance something
>>> else is off.
>>>
>>> On Thu, Mar 16, 2017 at
ounts I'm afraid you need to use
SERIAL or LOCAL_SERIAL (for in DC only accuracy)
On Thu, Mar 16, 2017 at 1:04 PM, srinivasarao daruna <sree.srin...@gmail.com
> wrote:
> Replication strategy is SimpleReplicationStrategy.
>
> Smith is : EC2 snitch. As we deployed cluster on EC2 insta
succeeds on node A a timestamp 1, B succeeds at timestamp 2
Read succeeds on node B and C at timestamp 1
If you need fully race condition free counts I'm afraid you need to use
SERIAL or LOCAL_SERIAL (for in DC only accuracy)
On Thu, Mar 16, 2017 at 1:04 PM, srinivasarao daruna <sree.srin..
his should cause the correct results to be returned.
You'll need to run a repair to fix the inconsistencies.
If all the data is actually there, you might have one or several nodes that
aren't identifying the correct replicas.
Arvydas
On Thu, Mar 16, 2017 at 5:31 PM, srinivasarao daruna <sree.srin..
Hi Team,
We are struggling with a problem related to cassandra counts, after backup
and restore of the cluster. Aaron Morton has suggested to send this to user
list, so some one of the list will be able to help me.
We are have a rest api to talk to cassandra and one of our query which
fetches
13 matches
Mail list logo
