Hey Michael,
In the case that you have a production cluster set up with multiple nodes,
assuming you have rf>1 it’s easier to just replace the broken node and restore
it’s data. (For future reference)
I wasn’t sure if view was referring to materialised view at the time although
Pradeeps
Check logs in your nodes, there could be GC or other issues causing
timeouts. This can happen for various reasons, network blips, node down,
node over loaded etc.
On Thu, Jun 7, 2018 at 6:16 AM, Saurav Suman wrote:
> Hi Team,
>
>
> I am getting below error in all the nodes of cassandra . Can
Hi,
we will follow the recommendation not to use materialized views.
Thanks a lot to both of you!
You helped me a lot.
Oh and besides: We are also using the lagom framework :) So we will also
be able to regenerate a Read-Side if have to.
greetings,
Michael
On 07.06.2018 13:45, Evelyn
Riccardo,
Simplest method can be is to add VPC as an additional datacenter to
existing cluster; once New DC has synced up all data, just switch over your
application. Only caveat is that there should be enough network bandwidth
between EC2 and VPC.
Horizontal scaling will help to some extent.
On Thu, Jun 7, 2018 at 9:12 AM, Nitan Kainth wrote:
> Riccardo,
>
> Simplest method can be is to add VPC as an additional datacenter to
> existing cluster; once New DC has synced up all data, just switch over your
> application. Only caveat is that there should be enough network bandwidth
>
I don't know about "new snitch protocol" (there is no snitch protocol), but
in the case of ec2snitch and gossipingpropertyfilesnitch (do not
extrapolate this to any other combination), you can switch them 1:1 before
the move, and everything should be fine, as long as care is taken to make
the
Jeff,
In this case, if Riccardo is adding new DC, then he can pickup new snitch
protocol right?
On Thu, Jun 7, 2018 at 12:15 PM, Jeff Jirsa wrote:
>
>
>
> On Thu, Jun 7, 2018 at 9:12 AM, Nitan Kainth
> wrote:
>
>> Riccardo,
>>
>> Simplest method can be is to add VPC as an additional
what is the schema version in Cassandra and for what are all the changes
schema version is changed?
why do we see schema version mismatch other than upgrades time?
Can we solve the schema version mismatch without restart the Cassandra nodes
--
Thanks & Regards,
Nanda Kishore
I meant migrating to gosspsnitch during adding new dc. New dc will be empty so
all the data will be streamed based on snitch property chosen
Sent from my iPhone
> On Jun 7, 2018, at 12:23 PM, Jeff Jirsa wrote:
>
> I don't know about "new snitch protocol" (there is no snitch protocol), but
>
Thanks Justin
On Thu, Jun 7, 2018 at 4:27 PM, Justin Cameron
wrote:
> You may run into schema mismatch issues if you make multiple schema
> alterations in a very short period of time (e.g. if you're programmatically
> modifying tables 50x a second). You'll be better off making schema changes
>
FYI
this is the info I got after research on schema version
what is the schema version in Cassandra and for what are all the changes
schema version is changed?
schema version is a UUID used to set a baseline version of the schema. It
tracks if a schema migration is required. Schema version
>
> I meant migrating to gosspsnitch during adding new dc. New dc will be
> empty so all the data will be streamed based on snitch property chosen
Should work fine on the new DC, as long as the original DC is using a
snitch that supports datacenters - then just don't mix and match snitches
You may run into schema mismatch issues if you make multiple schema
alterations in a very short period of time (e.g. if you're programmatically
modifying tables 50x a second). You'll be better off making schema changes
in advance. If you need to make dynamic changes then you could check the
Hi Expert,
I have questions about sstabledump
1,create table and insert data:
create table test2(a text,b text,primary key (a));
insert into test2(a,b) values ('a','b');
2,flush data to disk
3,sstabledump the sstable
[cassandra@concar-cassandra01]
Hi Team,
I am getting below error in all the nodes of cassandra . Can anyone let me know
what could be the cause. I am using apache cassandra 3.0.10.
Jun 06, 2018 2:59:04 PM com.google.common.cache.LocalCache$Segment$1 run
WARNING: Exception thrown during refresh
Dear list,
We have a small cluster on AWS EC2-Classic and we are planning to move it
to a VPC.
I know this has been discussed few times already including here:
16 matches
Mail list logo
