Rolling upgrade to 5.4 from 5.0 - "bug" caused by leader changes - is there a workaround?

[Michael Joyner <mi...@newsrx.com>]

Hello all,

I downloaded 5.4 and started doing a rolling upgrade from a 5.0 
solrcloud cluster and discovered that there seems to be a compatibility 
issue where doing a rolling upgrade from pre-5.4 which causes the 5.4 to 
fail with unable to determine leader errors.

Is there a work around that does not require taking the cluster down to 
upgrade to 5.4? Should I just stay with 5.3 for now? I need to implement 
programmatic schema changes in our collection via solrj, and based on 
what I'm reading this is a very new feature and requires the latest (or 
near latest) solrcloud.

Thanks!

-Mike

Re: Rolling upgrade to 5.4 from 5.0 - "bug" caused by leader changes - is there a workaround?

[Michael Joyner <mi...@newsrx.com>]

On 01/21/2016 01:22 PM, Ishan Chattopadhyaya wrote:
> Perhaps you could stay on 5.4.1 RC2, since that is what 5.4.1 will be
> (unless there are last moment issues).
>
> On Wed, Jan 20, 2016 at 7:50 PM, Michael Joyner <mi...@newsrx.com> wrote:
>
>> Unfortunately, it really couldn't wait.
>>
>> I did a rolling upgrade to the 5.4.1RC2 then downgraded everything to
>> 5.4.0 and so far everything seems fine.
>>
>> Couldn't take the cluster down.
>>
>>

I can wait for the 5.4.1 to be official as we are on the now official 
5.40 and so far all is well.

Though, I do find it odd that you can add a copy field declaration that 
duplicates an already existing declaration and one ends up with 
duplicate declarations...

Re: Rolling upgrade to 5.4 from 5.0 - "bug" caused by leader changes - is there a workaround?

[Ishan Chattopadhyaya <ic...@gmail.com>]

Perhaps you could stay on 5.4.1 RC2, since that is what 5.4.1 will be
(unless there are last moment issues).

On Wed, Jan 20, 2016 at 7:50 PM, Michael Joyner <mi...@newsrx.com> wrote:

> Unfortunately, it really couldn't wait.
>
> I did a rolling upgrade to the 5.4.1RC2 then downgraded everything to
> 5.4.0 and so far everything seems fine.
>
> Couldn't take the cluster down.
>
>
> On 01/19/2016 05:03 PM, Anshum Gupta wrote:
>
>> If you can wait, I'd suggest to be on the bug fix release. It should be
>> out
>> around the weekend.
>>
>> On Tue, Jan 19, 2016 at 1:48 PM, Michael Joyner <mi...@newsrx.com>
>> wrote:
>>
>> ok,
>>>
>>> I just found the 5.4.1 RC2 download, it seems to work ok for a rolling
>>> upgrade.
>>>
>>> I will see about downgrading back to 5.4.0 afterwards to be on an
>>> official
>>> release ...
>>>
>>>
>>>
>>> On 01/19/2016 04:27 PM, Michael Joyner wrote:
>>>
>>> Hello all,
>>>>
>>>> I downloaded 5.4 and started doing a rolling upgrade from a 5.0
>>>> solrcloud
>>>> cluster and discovered that there seems to be a compatibility issue
>>>> where
>>>> doing a rolling upgrade from pre-5.4 which causes the 5.4 to fail with
>>>> unable to determine leader errors.
>>>>
>>>> Is there a work around that does not require taking the cluster down to
>>>> upgrade to 5.4? Should I just stay with 5.3 for now? I need to implement
>>>> programmatic schema changes in our collection via solrj, and based on
>>>> what
>>>> I'm reading this is a very new feature and requires the latest (or near
>>>> latest) solrcloud.
>>>>
>>>> Thanks!
>>>>
>>>> -Mike
>>>>
>>>>
>>>
>>
>

Re: Rolling upgrade to 5.4 from 5.0 - "bug" caused by leader changes - is there a workaround?

[Michael Joyner <mi...@newsrx.com>]

Unfortunately, it really couldn't wait.

I did a rolling upgrade to the 5.4.1RC2 then downgraded everything to 
5.4.0 and so far everything seems fine.

Couldn't take the cluster down.

On 01/19/2016 05:03 PM, Anshum Gupta wrote:
> If you can wait, I'd suggest to be on the bug fix release. It should be out
> around the weekend.
>
> On Tue, Jan 19, 2016 at 1:48 PM, Michael Joyner <mi...@newsrx.com> wrote:
>
>> ok,
>>
>> I just found the 5.4.1 RC2 download, it seems to work ok for a rolling
>> upgrade.
>>
>> I will see about downgrading back to 5.4.0 afterwards to be on an official
>> release ...
>>
>>
>>
>> On 01/19/2016 04:27 PM, Michael Joyner wrote:
>>
>>> Hello all,
>>>
>>> I downloaded 5.4 and started doing a rolling upgrade from a 5.0 solrcloud
>>> cluster and discovered that there seems to be a compatibility issue where
>>> doing a rolling upgrade from pre-5.4 which causes the 5.4 to fail with
>>> unable to determine leader errors.
>>>
>>> Is there a work around that does not require taking the cluster down to
>>> upgrade to 5.4? Should I just stay with 5.3 for now? I need to implement
>>> programmatic schema changes in our collection via solrj, and based on what
>>> I'm reading this is a very new feature and requires the latest (or near
>>> latest) solrcloud.
>>>
>>> Thanks!
>>>
>>> -Mike
>>>
>>
>

Re: Rolling upgrade to 5.4 from 5.0 - "bug" caused by leader changes - is there a workaround?

[Anshum Gupta <an...@anshumgupta.net>]

If you can wait, I'd suggest to be on the bug fix release. It should be out
around the weekend.

On Tue, Jan 19, 2016 at 1:48 PM, Michael Joyner <mi...@newsrx.com> wrote:

> ok,
>
> I just found the 5.4.1 RC2 download, it seems to work ok for a rolling
> upgrade.
>
> I will see about downgrading back to 5.4.0 afterwards to be on an official
> release ...
>
>
>
> On 01/19/2016 04:27 PM, Michael Joyner wrote:
>
>> Hello all,
>>
>> I downloaded 5.4 and started doing a rolling upgrade from a 5.0 solrcloud
>> cluster and discovered that there seems to be a compatibility issue where
>> doing a rolling upgrade from pre-5.4 which causes the 5.4 to fail with
>> unable to determine leader errors.
>>
>> Is there a work around that does not require taking the cluster down to
>> upgrade to 5.4? Should I just stay with 5.3 for now? I need to implement
>> programmatic schema changes in our collection via solrj, and based on what
>> I'm reading this is a very new feature and requires the latest (or near
>> latest) solrcloud.
>>
>> Thanks!
>>
>> -Mike
>>
>
>


-- 
Anshum Gupta

Re: Rolling upgrade to 5.4 from 5.0 - "bug" caused by leader changes - is there a workaround?

[Michael Joyner <mi...@newsrx.com>]

ok,

I just found the 5.4.1 RC2 download, it seems to work ok for a rolling 
upgrade.

I will see about downgrading back to 5.4.0 afterwards to be on an 
official release ...


On 01/19/2016 04:27 PM, Michael Joyner wrote:
> Hello all,
>
> I downloaded 5.4 and started doing a rolling upgrade from a 5.0 
> solrcloud cluster and discovered that there seems to be a 
> compatibility issue where doing a rolling upgrade from pre-5.4 which 
> causes the 5.4 to fail with unable to determine leader errors.
>
> Is there a work around that does not require taking the cluster down 
> to upgrade to 5.4? Should I just stay with 5.3 for now? I need to 
> implement programmatic schema changes in our collection via solrj, and 
> based on what I'm reading this is a very new feature and requires the 
> latest (or near latest) solrcloud.
>
> Thanks!
>
> -Mike

Re: Rolling upgrade to 5.4 from 5.0 - "bug" caused by leader changes - is there a workaround?

[Anshum Gupta <an...@anshumgupta.net>]

Hi Mike,

This is a known issue and would be fixed with the upcoming 5.4.1.
Here's a link to the issue: https://issues.apache.org/jira/browse/SOLR-8561

On Tue, Jan 19, 2016 at 1:27 PM, Michael Joyner <mi...@newsrx.com> wrote:

> Hello all,
>
> I downloaded 5.4 and started doing a rolling upgrade from a 5.0 solrcloud
> cluster and discovered that there seems to be a compatibility issue where
> doing a rolling upgrade from pre-5.4 which causes the 5.4 to fail with
> unable to determine leader errors.
>
> Is there a work around that does not require taking the cluster down to
> upgrade to 5.4? Should I just stay with 5.3 for now? I need to implement
> programmatic schema changes in our collection via solrj, and based on what
> I'm reading this is a very new feature and requires the latest (or near
> latest) solrcloud.
>
> Thanks!
>
> -Mike
>



-- 
Anshum Gupta