Re: Try version 3.11

[Michael Shuler]

On 05/06/2017 07:04 AM, Cogumelos Maravilha wrote:
> Hi all,
> 
> deb http://www.apache.org/dist/cassandra/debian 310x main
> deb http://www.apache.org/dist/cassandra/debian 311x main
> deb http://www.apache.org/dist/cassandra/debian sid main
> deb http://www.apache.org/dist/cassandra/debian unstable main
> 
> Is there a way to try C* version 3.11 binary before release date?

You have a couple options:

- grab the latest tar build from CI:
  http://cassci.datastax.com/job/cassandra-3.11/lastBuild/

- build your own debs from the `cassandra-3.11` branch:
  https://github.com/apache/cassandra-builds

The project is working through snapshot package builds, but those don't
exist, yet.

-- 
Kind regards,
Michael

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Re: Cassandra Schema version mismatch

[Carlos Rolo]

Sometimes "resetlocalschema" (happened to me, didn't check why) will not
work, and you need to stop the offending nodes and bring them back one by
one.. That solved the issue.

In the cases I've seen this happened the clusters in question where either:

a) A couple of nodes down (cloud provider caused a partial outage) with an
application that would create/change tables every now and then
b) Massive GC pauses around the cluster with a schema change being tried
over and over.

CQLSH stopped working, your nodes died? GC Pauses? Operator mistake?

Regards,

Carlos Juzarte Rolo
Cassandra Consultant / Datastax Certified Architect / Cassandra MVP

Pythian - Love your data

rolo@pythian | Twitter: @cjrolo | Skype: cjr2k3 | Linkedin:
*linkedin.com/in/carlosjuzarterolo
*
Mobile: +351 918 918 100
www.pythian.com

On Sat, May 6, 2017 at 1:07 PM, Nitan Kainth  wrote:

> Thank you Jeff.
>
> James,
>
> We started getting insufficient replica errors. Cqlsh stopped working for
> two nodes .
>
> Sent from my iPhone
>
> > On May 5, 2017, at 7:13 PM, James Rothering 
> wrote:
> >
> > I've heard about this ... how did the problem present itself?
> >
> > Sent from my iPhone
> >
> >> On May 5, 2017, at 3:17 PM, Jeff Jirsa  wrote:
> >>
> >>
> >>
> >>> On 2017-05-05 11:00 (-0700), Nitan Kainth  wrote:
> >>> Hi Experts,
> >>>
> >>> We found schema version mismatch in our cluster. We fixed it by
> bouncing C* on nodes where version was mismatched. Can someone suggest,
> what are the possible reasons for this? We are trying to figure out the
> root cause.
> >>>
> >>
> >> Do all of your versions match? You didn't accidentally upgrade half the
> cluster did you?
> >>
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
> >> For additional commands, e-mail: user-h...@cassandra.apache.org
> >>
> >
> > -
> > To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
> > For additional commands, e-mail: user-h...@cassandra.apache.org
> >
>
> -
> To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: user-h...@cassandra.apache.org
>
>

-- 


--

Re: Cassandra Schema version mismatch

[Nitan Kainth]

Thank you Jeff.

James, 

We started getting insufficient replica errors. Cqlsh stopped working for two 
nodes .

Sent from my iPhone

> On May 5, 2017, at 7:13 PM, James Rothering  wrote:
> 
> I've heard about this ... how did the problem present itself?
> 
> Sent from my iPhone
> 
>> On May 5, 2017, at 3:17 PM, Jeff Jirsa  wrote:
>> 
>> 
>> 
>>> On 2017-05-05 11:00 (-0700), Nitan Kainth  wrote: 
>>> Hi Experts,
>>> 
>>> We found schema version mismatch in our cluster. We fixed it by bouncing C* 
>>> on nodes where version was mismatched. Can someone suggest, what are the 
>>> possible reasons for this? We are trying to figure out the root cause.
>>> 
>> 
>> Do all of your versions match? You didn't accidentally upgrade half the 
>> cluster did you?
>> 
>> 
>> 
>> -
>> To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
>> For additional commands, e-mail: user-h...@cassandra.apache.org
>> 
> 
> -
> To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: user-h...@cassandra.apache.org
> 

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Try version 3.11

[Cogumelos Maravilha]

Hi all,

deb http://www.apache.org/dist/cassandra/debian 310x main
deb http://www.apache.org/dist/cassandra/debian 311x main
deb http://www.apache.org/dist/cassandra/debian sid main
deb http://www.apache.org/dist/cassandra/debian unstable main

Is there a way to try C* version 3.11 binary before release date?

Thanks


-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Re: manual deletes with TWCS

[Alexander Dejanovski]

Hi John,

if all your data is TTLed then you'll be fine and purge should happen in
due time as long as your sstables don't overlap on timestamp (which can
only happen through repair mechanisms).
The tombstones will get purged when the ssatble that contain them also
fully expire.

Cheers

Le ven. 5 mai 2017 à 23:04, John Sanda  a écrit :

> This is involving TTLed data, and I actually would want to delete all
> related partitions across all time windows. Let's say I have a time series
> partitioned by day with a 7 day TTL and a window size of one day. If I
> delete partitions for the past seven days, would I still run into the issue
> of data purge being postponed?
>
> On Fri, May 5, 2017 at 4:57 PM, Jon Haddad 
> wrote:
>
>> You cannot.
>>
>> From Alex’s TLP post:
>> http://thelastpickle.com/blog/2016/12/08/TWCS-part1.html
>>
>> TWCS is no fit for workload that perform deletes on non TTLed data.
>> Consider that SSTables from different time windows will never be compacted
>> together, so data inserted on day 1 and deleted on day 2 will have the
>> tombstone and the shadowed cells living in different time windows. Unless a
>> major compaction is performed (which shouldn’t), and while the deletion
>> will seem effective when running queries, space will never be reclaimed on
>> disk.
>> Deletes can be performed on TTLed data if needed, but the partition will
>> then exist in different time windows, which will postpone actual deletion
>> from disk until both time windows fully expire.
>>
>>
>> On May 5, 2017, at 1:54 PM, John Sanda  wrote:
>>
>> How problematic is it to perform deletes when using TWCS? I am currently
>> using TWCS and have some new use cases for performing deletes. So far I
>> have avoided performing deletes, but I am wondering what issues I might run
>> into.
>>
>>
>> - John
>>
>>
>>
>
>
> --
>
> - John
>
-- 
-
Alexander Dejanovski
France
@alexanderdeja

Consultant
Apache Cassandra Consulting
http://www.thelastpickle.com