Re: NGCC?

[Nate McCall]

>
> Mid-to-late September is good, but so is October.

The community-driven Cassandra Japan conference is tentatively
targeting the first week of October. We've had participants from Japan
the past couple of years at NGCC, so would be cool if we could
accommodate that.

+1 on Mid September. (We should probably move this to a vote/form thingy soon).

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

Re: NGCC?

[Jonathan Haddad]

+1.

Are there guidelines for how to set something like this up or is it tribal
knowledge?

On Wed, May 31, 2017 at 3:05 PM Gary Dusbabek  wrote:

> +1. I'm happy to help with logistics.
>
> Mid-to-late September is good, but so is October.
>
> Gary.
>
> On Wed, May 31, 2017 at 2:19 PM, Eric Evans 
> wrote:
>
> > Hi,
> >
> > Is anyone working on an NGCC event for this year? Given all of the
> > recent changes, it seems like it could be really useful. If not, is
> > there interest? When would be good, September? October? What about
> > location? I think we could get the space to host such an even in
> > either San Antonio (centrally located), or San Francisco (San
> > Franciscoly located).
> >
> > Thoughts?
> >
> > --
> > Eric Evans
> > john.eric.ev...@gmail.com
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> > For additional commands, e-mail: dev-h...@cassandra.apache.org
> >
> >
>

Re: NGCC?

[Gary Dusbabek]

+1. I'm happy to help with logistics.

Mid-to-late September is good, but so is October.

Gary.

On Wed, May 31, 2017 at 2:19 PM, Eric Evans 
wrote:

> Hi,
>
> Is anyone working on an NGCC event for this year? Given all of the
> recent changes, it seems like it could be really useful. If not, is
> there interest? When would be good, September? October? What about
> location? I think we could get the space to host such an even in
> either San Antonio (centrally located), or San Francisco (San
> Franciscoly located).
>
> Thoughts?
>
> --
> Eric Evans
> john.eric.ev...@gmail.com
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
>
>

NGCC?

[Eric Evans]

Hi,

Is anyone working on an NGCC event for this year? Given all of the
recent changes, it seems like it could be really useful. If not, is
there interest? When would be good, September? October? What about
location? I think we could get the space to host such an even in
either San Antonio (centrally located), or San Francisco (San
Franciscoly located).

Thoughts?

-- 
Eric Evans
john.eric.ev...@gmail.com

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

Re: Potential block issue for 3.0.13: schema version id mismatch while upgrading

[J. D. Jordan]

I would guess there are way fewer people who have already upgraded than people 
who haven't. So better  to fix this as fast as possible and cut a release than 
wait longer and not. At the very least we should pull 3.0.13 so even less 
people can/have upgrade to it.

> On May 31, 2017, at 7:45 AM, Jeff Jirsa  wrote:
> 
> The number of people isn't zero. Before we commit and cut a new release, we 
> need to be able to explain what that upgrade path is.
> 
> If this is just migration storms then it's not worth cutting a new release - 
> 3.0 was doing that anyway until very recently. If it fails to start that's a 
> much bigger problem, but I don't see why (without testing this myself first) 
> why it would fail to start on the minor version upgrade. Can someone explain 
> why we get unknown cfid just be changing the digest order?
> 
> 
> -- 
> Jeff Jirsa
> 
> 
>> On May 31, 2017, at 12:34 AM, Stefania Alborghetti 
>>  wrote:
>> 
>> The patch for 13559 is available if we want to release it in 3.0.14. The
>> tests are still running but I don't expect problems. We need a reviewer
>> however.
>> 
>> Releasing the patch in 3.0.14 will cause problems for people that deployed
>> 3.0.13 and upgrade upwards, but the schema will agree once the rolling
>> upgrade is over. There shouldn't be too many people with 3.0.13 in
>> production however, since upgrading to 3.0.13 is broken in the first place.
>> 
>> Our upgrade tests totally missed this, so they should be checked as to why
>> this is the case.
>> 
>> 
>>> On Wed, May 31, 2017 at 12:34 PM, kurt greaves  wrote:
>>> 
>>> On 31 May 2017 at 03:41, Jeremiah D Jordan 
>>> wrote:
>>> 
 If 3.0.13 causes schema mismatch on upgrade, then maybe we should pull
 that and release 3.0.14 once 13559 is fixed.  As that is a pretty bad
>>> place
 to get into.
>>> 
>>> 
>>> i think that would be a good idea
>>> 
>> 
>> 
>> 
>> -- 
>> 
>> 
>> 
>> STEFANIA ALBORGHETTI
>> 
>> Software engineer | +852 6114 9265 | stefania.alborghe...@datastax.com
>> 
>> 
>> [image: http://www.datastax.com/cloud-applications]
>> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
> 

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

Re: Potential block issue for 3.0.13: schema version id mismatch while upgrading

[Jeff Jirsa]

The number of people isn't zero. Before we commit and cut a new release, we 
need to be able to explain what that upgrade path is.

If this is just migration storms then it's not worth cutting a new release - 
3.0 was doing that anyway until very recently. If it fails to start that's a 
much bigger problem, but I don't see why (without testing this myself first) 
why it would fail to start on the minor version upgrade. Can someone explain 
why we get unknown cfid just be changing the digest order?


-- 
Jeff Jirsa


> On May 31, 2017, at 12:34 AM, Stefania Alborghetti 
>  wrote:
> 
> The patch for 13559 is available if we want to release it in 3.0.14. The
> tests are still running but I don't expect problems. We need a reviewer
> however.
> 
> Releasing the patch in 3.0.14 will cause problems for people that deployed
> 3.0.13 and upgrade upwards, but the schema will agree once the rolling
> upgrade is over. There shouldn't be too many people with 3.0.13 in
> production however, since upgrading to 3.0.13 is broken in the first place.
> 
> Our upgrade tests totally missed this, so they should be checked as to why
> this is the case.
> 
> 
>> On Wed, May 31, 2017 at 12:34 PM, kurt greaves  wrote:
>> 
>> On 31 May 2017 at 03:41, Jeremiah D Jordan 
>> wrote:
>> 
>>> If 3.0.13 causes schema mismatch on upgrade, then maybe we should pull
>>> that and release 3.0.14 once 13559 is fixed.  As that is a pretty bad
>> place
>>> to get into.
>> 
>> 
>> i think that would be a good idea
>> 
> 
> 
> 
> -- 
> 
> 
> 
> STEFANIA ALBORGHETTI
> 
> Software engineer | +852 6114 9265 | stefania.alborghe...@datastax.com
> 
> 
> [image: http://www.datastax.com/cloud-applications]
> 

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

Re: Potential block issue for 3.0.13: schema version id mismatch while upgrading

[Stefan Podkowinski]

On 31.05.2017 09:34, Stefania Alborghetti wrote:
> There shouldn't be too many people with 3.0.13 in
> production however, since upgrading to 3.0.13 is broken in the first place.

Keep in mind that there are always people upgrading from 2.x, especially
since we had a couple of important bug fixes for 2.x -> 3.0 that people
might have been waiting for before taking the plunge. We should at least
be so kind to let these users know about potential issues in NEWS.txt.

If I understand correctly, this will cause schema migration storms
across nodes for .13 -> .14. I'd rather see us pulling 3.0.13 from
downloads now and take some more time to figure out what can be done for
users already running 3.0.13 on production, instead of rushing .14 and
risk throwing .13 users under the bus.

E.g. can we create a nodetool command to disable execution of schema
migration tasks, which can be run during cluster upgrades in cases like
this?



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

Re: Potential block issue for 3.0.13: schema version id mismatch while upgrading

[Stefania Alborghetti]

The patch for 13559 is available if we want to release it in 3.0.14. The
tests are still running but I don't expect problems. We need a reviewer
however.

Releasing the patch in 3.0.14 will cause problems for people that deployed
3.0.13 and upgrade upwards, but the schema will agree once the rolling
upgrade is over. There shouldn't be too many people with 3.0.13 in
production however, since upgrading to 3.0.13 is broken in the first place.

Our upgrade tests totally missed this, so they should be checked as to why
this is the case.


On Wed, May 31, 2017 at 12:34 PM, kurt greaves  wrote:

> On 31 May 2017 at 03:41, Jeremiah D Jordan 
> wrote:
>
> > If 3.0.13 causes schema mismatch on upgrade, then maybe we should pull
> > that and release 3.0.14 once 13559 is fixed.  As that is a pretty bad
> place
> > to get into.
>
>
> i think that would be a good idea
>



-- 



STEFANIA ALBORGHETTI

Software engineer | +852 6114 9265 | stefania.alborghe...@datastax.com


[image: http://www.datastax.com/cloud-applications]