Re: Introducing Cassandra 3.7 LTS

[Kai Wang]

This is awesome! Stability is the king.

Thank you so much!

On Oct 19, 2016 2:56 PM, "Ben Bromhead"  wrote:

> Hi All
>
> I am proud to announce we are making available our production build of
> Cassandra 3.7 that we run at Instaclustr (both for ourselves and our
> customers). Our release of Cassandra 3.7 includes a number of backported
> patches from later versions of Cassandra e.g. 3.8 and 3.9 but doesn't
> include the new features of these releases.
>
> You can find our release of Cassandra 3.7 LTS on github here (
> https://github.com/instaclustr/cassandra). You can read more of our
> thinking and how this applies to our managed service here (
> https://www.instaclustr.com/blog/2016/10/19/patched-cassandra-3-7/).
>
> We also have an expanded FAQ about why and how we are approaching 3.x in
> this manner (https://github.com/instaclustr/cassandra#cassandra-37-lts),
> however I've included the top few question and answers below:
>
> *Is this a fork?*
> No, This is just Cassandra with a different release cadence for those who
> want 3.x features but are slightly more risk averse than the current
> schedule allows.
>
> *Why not just use the official release?*
> With the 3.x tick-tock branch we have encountered more instability than
> with the previous release cadence. We feel that releasing new features
> every other release makes it very hard for operators to stabilize their
> production environment without bringing in brand new features that are not
> battle tested. With the release of Cassandra 3.8 and 3.9 simultaneously the
> bug fix branch included new and real-world untested features, specifically
> CDC. We have decided to stick with Cassandra 3.7 and instead backport
> critical issues and maintain it ourselves rather than trying to stick with
> the current Apache Cassandra release cadence.
>
> *Why backport?*
> At Instaclustr we support and run a number of different versions of Apache
> Cassandra on behalf of our customers. Over the course of managing Cassandra
> for our customers we often encounter bugs. There are existing patches for
> some of them, others we patch ourselves. Generally, if we can, we try to
> wait for the next official Apache Cassandra release, however in the need to
> ensure our customers remain stable and running we will sometimes backport
> bugs and write our own hotfixes (which are also submitted back to the
> community).
>
> *Why release it?*
> A number of our customers and people in the community have asked if we
> would make this available, which we are more than happy to do so. This
> repository represents what Instaclustr runs in production for Cassandra 3.7
> and this is our way of helping the community get a similar level of
> stability as what you would get from our managed service.
>
> Cheers
>
> Ben
>
>
>
> --
> Ben Bromhead
> CTO | Instaclustr 
> +1 650 284 9692
> Managed Cassandra / Spark on AWS, Azure and Softlayer
>

Re: Rebuild failing while adding new datacenter

[Jai Bheemsen Rao Dhanwada]

I have opened https://issues.apache.org/jira/browse/CASSANDRA-12816


On Thu, Oct 20, 2016 at 6:30 PM, Yabin Meng  wrote:

> Sorry, I'm not aware of it
>
> On Thu, Oct 20, 2016 at 6:00 PM, Jai Bheemsen Rao Dhanwada <
> jaibheem...@gmail.com> wrote:
>
>> Thank you Yabin, is there a exisiting JIRA that I can refer to?
>>
>> On Thu, Oct 20, 2016 at 2:05 PM, Yabin Meng  wrote:
>>
>>> I have seen this on other releases, on 2.2.x. The workaround is exactly
>>> like yours,  some other system keyspaces also need similar changes.
>>>
>>> I would say this is a benign bug.
>>>
>>> Yabin
>>>
>>> On Thu, Oct 20, 2016 at 4:41 PM, Jai Bheemsen Rao Dhanwada <
>>> jaibheem...@gmail.com> wrote:
>>>
 thanks,

 This always works on 2.1.13 and 2.1.16 version but not on 3.0.8.
 definitely not a firewall issue

 On Thu, Oct 20, 2016 at 1:16 PM, sai krishnam raju potturi <
 pskraj...@gmail.com> wrote:

> we faced a similar issue earlier, but that was more related to
> firewall rules. The newly added datacenter was not able to communicate 
> with
> the existing datacenters on the port 7000(inter-node communication). 
> Your's
> might be a different issue, but just saying.
>
>
> On Thu, Oct 20, 2016 at 4:12 PM, Jai Bheemsen Rao Dhanwada <
> jaibheem...@gmail.com> wrote:
>
>> Hello All,
>>
>> I have single datacenter with 3 C* nodes and we are trying to expand
>> the cluster to another region/DC. I am seeing the below error while 
>> doing a
>> "nodetool rebuild -- name_of_existing_data_center" .
>>
>> [user@machine ~]$ nodetool rebuild DC1
>> nodetool: Unable to find sufficient sources for streaming range
>> (-402178150752044282,-396707578307430827] in keyspace
>> system_distributed
>> See 'nodetool help' or 'nodetool help '.
>> [user@machine ~]$
>>
>> user@cqlsh> SELECT * from system_schema.keyspaces where
>> keyspace_name='system_distributed';
>>
>>  keyspace_name | durable_writes | replication
>> ---++---
>> --
>>  system_distributed |   True | {'class':
>> 'org.apache.cassandra.locator.SimpleStrategy', 'replication_factor':
>> '3'}
>>
>> (1 rows)
>>
>> To overcome this I have updated system_distributed keyspace to DC1:3
>> and DC2:3 with NetworkTopologyStrategy
>>
>> C* Version - 3.0.8
>>
>> Is this a bug that is introduced in 3.0.8 version of cassandra? as I
>> haven't seen this issue with the older versions?
>>
>
>

>>>
>>
>