Re: SOLR upgrade

[David Hastings]

i generally will only upgrade every other release.  since i started with
1.4, went to 3->5->7.X, and never EVER a .0 or an even .X release,

On Fri, Feb 12, 2021 at 12:01 PM Ishan Chattopadhyaya <
ichattopadhy...@gmail.com> wrote:

> Just avoid 8.8.0 for the moment, until 8.8.1 is released. 8.7.x should be
> fine.
>
> On Fri, Feb 12, 2021 at 10:28 PM Alessandro Benedetti <
> a.benede...@sease.io>
> wrote:
>
> > Hi,
> > following up on Charlie's detailed response I would recommend carefully
> > assess the code you are using to interact with Apache Solr (on top of the
> > Solr changes themselves).
> > Assuming you are using some sort of client, it's extremely important to
> > fully understand both the syntax and semantic of each call.
> > I saw a lot of "compiling ok" search-api migrations that were ok
> > syntactically but doing a disaster from the semantic perspective (missing
> > important parameters ect).
> >
> > In case you have plugins to maintain this would be even more complicated
> > than just make them compile.
> >
> > Regards
> > --
> > Alessandro Benedetti
> > Apache Lucene/Solr Committer
> > Director, R&D Software Engineer, Search Consultant
> > www.sease.io
> >
> >
> > On Tue, 9 Feb 2021 at 11:01, Charlie Hull <
> ch...@opensourceconnections.com
> > >
> > wrote:
> >
> > > Hi Lulu,
> > >
> > > I'm afraid you're going to have to recognise that Solr 5.2.1 is very
> > > out-of-date and the changes between this version and the current 8.x
> > > releases are significant. A direct jump is I think the only sensible
> > > option.
> > >
> > > Although you could take the current configuration and attempt to
> upgrade
> > > it to work with 8.x, I recommend that you should take the chance to
> look
> > > at your whole infrastructure (from data ingestion through to query
> > > construction) and consider what needs upgrading/redesigning for both
> > > performance and future-proofing. You shouldn't just attempt a
> > > lift-and-shift of the current setup - some things just won't work and
> > > some may lock you into future issues. If you're running at large scale
> > > (I've talked to some people at the BL before and I know you have some
> > > huge indexes there!) then a redesign may be necessary for scalability
> > > reasons (cost and feasibility). You should also consider your skills
> > > base and how the team can stay up to date with Solr changes and modern
> > > search practice.
> > >
> > > Hope this helps - this is a common situation which I've seen many times
> > > before, you're certainly not the oldest version of Solr running I've
> > > seen recently either!
> > >
> > > best
> > >
> > > Charlie
> > >
> > > On 09/02/2021 01:14, Paul, Lulu wrote:
> > > > Hi SOLR team,
> > > >
> > > > Please may I ask for advice regarding upgrading the SOLR version (our
> > > project currently running on solr-5.2.1) to the latest version?
> > > > What are the steps, breaking changes and potential issues ? Could
> this
> > > be done as an incremental version upgrade or a direct jump to the
> newest
> > > version?
> > > >
> > > > Much appreciate the advice, Thank you!
> > > >
> > > > Best Wishes
> > > > Lulu
> > > >
> > > >
> > > >
> > >
> >
> **
> > > > Experience the British Library online at www.bl.uk >
> > > > The British Library's latest Annual Report and Accounts :
> > > www.bl.uk/aboutus/annrep/index.html<
> > > http://www.bl.uk/aboutus/annrep/index.html>
> > > > Help the British Library conserve the world's knowledge. Adopt a
> Book.
> > > www.bl.uk/adoptabook
> > > > The Library's St Pancras site is WiFi - enabled
> > > >
> > >
> >
> *
> > > > The information contained in this e-mail is confidential and may be
> > > legally privileged. It is intended for the addressee(s) only. If you
> are
> > > not the intended recipient, please delete this e-mail and notify the
> > > postmas...@bl.uk : The contents of this
> e-mail
> > > must not be disclosed or copied without the sender's consent.
> > > > The statements and opinions expressed in this message are those of
> the
> > > author and do not necessarily reflect those of the British Library. The
> > > British Library does not take any responsibility for the views of the
> > > author.
> > > >
> > >
> >
> *
> > > > Think before you print
> > > >
> > >
> > > --
> > > Charlie Hull - Managing Consultant at OpenSource Connections Limited
> > > 
> > > Founding member of The Search Network 
> > > and co-author of Searching the Enterprise
> > > 
> > > tel/fax: +4

Re: SOLR upgrade

[Ishan Chattopadhyaya]

Just avoid 8.8.0 for the moment, until 8.8.1 is released. 8.7.x should be
fine.

On Fri, Feb 12, 2021 at 10:28 PM Alessandro Benedetti 
wrote:

> Hi,
> following up on Charlie's detailed response I would recommend carefully
> assess the code you are using to interact with Apache Solr (on top of the
> Solr changes themselves).
> Assuming you are using some sort of client, it's extremely important to
> fully understand both the syntax and semantic of each call.
> I saw a lot of "compiling ok" search-api migrations that were ok
> syntactically but doing a disaster from the semantic perspective (missing
> important parameters ect).
>
> In case you have plugins to maintain this would be even more complicated
> than just make them compile.
>
> Regards
> --
> Alessandro Benedetti
> Apache Lucene/Solr Committer
> Director, R&D Software Engineer, Search Consultant
> www.sease.io
>
>
> On Tue, 9 Feb 2021 at 11:01, Charlie Hull  >
> wrote:
>
> > Hi Lulu,
> >
> > I'm afraid you're going to have to recognise that Solr 5.2.1 is very
> > out-of-date and the changes between this version and the current 8.x
> > releases are significant. A direct jump is I think the only sensible
> > option.
> >
> > Although you could take the current configuration and attempt to upgrade
> > it to work with 8.x, I recommend that you should take the chance to look
> > at your whole infrastructure (from data ingestion through to query
> > construction) and consider what needs upgrading/redesigning for both
> > performance and future-proofing. You shouldn't just attempt a
> > lift-and-shift of the current setup - some things just won't work and
> > some may lock you into future issues. If you're running at large scale
> > (I've talked to some people at the BL before and I know you have some
> > huge indexes there!) then a redesign may be necessary for scalability
> > reasons (cost and feasibility). You should also consider your skills
> > base and how the team can stay up to date with Solr changes and modern
> > search practice.
> >
> > Hope this helps - this is a common situation which I've seen many times
> > before, you're certainly not the oldest version of Solr running I've
> > seen recently either!
> >
> > best
> >
> > Charlie
> >
> > On 09/02/2021 01:14, Paul, Lulu wrote:
> > > Hi SOLR team,
> > >
> > > Please may I ask for advice regarding upgrading the SOLR version (our
> > project currently running on solr-5.2.1) to the latest version?
> > > What are the steps, breaking changes and potential issues ? Could this
> > be done as an incremental version upgrade or a direct jump to the newest
> > version?
> > >
> > > Much appreciate the advice, Thank you!
> > >
> > > Best Wishes
> > > Lulu
> > >
> > >
> > >
> >
> **
> > > Experience the British Library online at www.bl.uk
> > > The British Library's latest Annual Report and Accounts :
> > www.bl.uk/aboutus/annrep/index.html<
> > http://www.bl.uk/aboutus/annrep/index.html>
> > > Help the British Library conserve the world's knowledge. Adopt a Book.
> > www.bl.uk/adoptabook
> > > The Library's St Pancras site is WiFi - enabled
> > >
> >
> *
> > > The information contained in this e-mail is confidential and may be
> > legally privileged. It is intended for the addressee(s) only. If you are
> > not the intended recipient, please delete this e-mail and notify the
> > postmas...@bl.uk : The contents of this e-mail
> > must not be disclosed or copied without the sender's consent.
> > > The statements and opinions expressed in this message are those of the
> > author and do not necessarily reflect those of the British Library. The
> > British Library does not take any responsibility for the views of the
> > author.
> > >
> >
> *
> > > Think before you print
> > >
> >
> > --
> > Charlie Hull - Managing Consultant at OpenSource Connections Limited
> > 
> > Founding member of The Search Network 
> > and co-author of Searching the Enterprise
> > 
> > tel/fax: +44 (0)8700 118334
> > mobile: +44 (0)7767 825828
> >
>

Re: SOLR upgrade

[Alessandro Benedetti]

Hi,
following up on Charlie's detailed response I would recommend carefully
assess the code you are using to interact with Apache Solr (on top of the
Solr changes themselves).
Assuming you are using some sort of client, it's extremely important to
fully understand both the syntax and semantic of each call.
I saw a lot of "compiling ok" search-api migrations that were ok
syntactically but doing a disaster from the semantic perspective (missing
important parameters ect).

In case you have plugins to maintain this would be even more complicated
than just make them compile.

Regards
--
Alessandro Benedetti
Apache Lucene/Solr Committer
Director, R&D Software Engineer, Search Consultant
www.sease.io


On Tue, 9 Feb 2021 at 11:01, Charlie Hull 
wrote:

> Hi Lulu,
>
> I'm afraid you're going to have to recognise that Solr 5.2.1 is very
> out-of-date and the changes between this version and the current 8.x
> releases are significant. A direct jump is I think the only sensible
> option.
>
> Although you could take the current configuration and attempt to upgrade
> it to work with 8.x, I recommend that you should take the chance to look
> at your whole infrastructure (from data ingestion through to query
> construction) and consider what needs upgrading/redesigning for both
> performance and future-proofing. You shouldn't just attempt a
> lift-and-shift of the current setup - some things just won't work and
> some may lock you into future issues. If you're running at large scale
> (I've talked to some people at the BL before and I know you have some
> huge indexes there!) then a redesign may be necessary for scalability
> reasons (cost and feasibility). You should also consider your skills
> base and how the team can stay up to date with Solr changes and modern
> search practice.
>
> Hope this helps - this is a common situation which I've seen many times
> before, you're certainly not the oldest version of Solr running I've
> seen recently either!
>
> best
>
> Charlie
>
> On 09/02/2021 01:14, Paul, Lulu wrote:
> > Hi SOLR team,
> >
> > Please may I ask for advice regarding upgrading the SOLR version (our
> project currently running on solr-5.2.1) to the latest version?
> > What are the steps, breaking changes and potential issues ? Could this
> be done as an incremental version upgrade or a direct jump to the newest
> version?
> >
> > Much appreciate the advice, Thank you!
> >
> > Best Wishes
> > Lulu
> >
> >
> >
> **
> > Experience the British Library online at www.bl.uk
> > The British Library's latest Annual Report and Accounts :
> www.bl.uk/aboutus/annrep/index.html<
> http://www.bl.uk/aboutus/annrep/index.html>
> > Help the British Library conserve the world's knowledge. Adopt a Book.
> www.bl.uk/adoptabook
> > The Library's St Pancras site is WiFi - enabled
> >
> *
> > The information contained in this e-mail is confidential and may be
> legally privileged. It is intended for the addressee(s) only. If you are
> not the intended recipient, please delete this e-mail and notify the
> postmas...@bl.uk : The contents of this e-mail
> must not be disclosed or copied without the sender's consent.
> > The statements and opinions expressed in this message are those of the
> author and do not necessarily reflect those of the British Library. The
> British Library does not take any responsibility for the views of the
> author.
> >
> *
> > Think before you print
> >
>
> --
> Charlie Hull - Managing Consultant at OpenSource Connections Limited
> 
> Founding member of The Search Network 
> and co-author of Searching the Enterprise
> 
> tel/fax: +44 (0)8700 118334
> mobile: +44 (0)7767 825828
>

Re: SOLR upgrade

[Charlie Hull]

Hi Lulu,

I'm afraid you're going to have to recognise that Solr 5.2.1 is very 
out-of-date and the changes between this version and the current 8.x 
releases are significant. A direct jump is I think the only sensible 
option.


Although you could take the current configuration and attempt to upgrade 
it to work with 8.x, I recommend that you should take the chance to look 
at your whole infrastructure (from data ingestion through to query 
construction) and consider what needs upgrading/redesigning for both 
performance and future-proofing. You shouldn't just attempt a 
lift-and-shift of the current setup - some things just won't work and 
some may lock you into future issues. If you're running at large scale 
(I've talked to some people at the BL before and I know you have some 
huge indexes there!) then a redesign may be necessary for scalability 
reasons (cost and feasibility). You should also consider your skills 
base and how the team can stay up to date with Solr changes and modern 
search practice.


Hope this helps - this is a common situation which I've seen many times 
before, you're certainly not the oldest version of Solr running I've 
seen recently either!


best

Charlie

On 09/02/2021 01:14, Paul, Lulu wrote:

Hi SOLR team,

Please may I ask for advice regarding upgrading the SOLR version (our project 
currently running on solr-5.2.1) to the latest version?
What are the steps, breaking changes and potential issues ? Could this be done 
as an incremental version upgrade or a direct jump to the newest version?

Much appreciate the advice, Thank you!

Best Wishes
Lulu


**
Experience the British Library online at www.bl.uk
The British Library's latest Annual Report and Accounts : 
www.bl.uk/aboutus/annrep/index.html
Help the British Library conserve the world's knowledge. Adopt a Book. 
www.bl.uk/adoptabook
The Library's St Pancras site is WiFi - enabled
*
The information contained in this e-mail is confidential and may be legally 
privileged. It is intended for the addressee(s) only. If you are not the intended 
recipient, please delete this e-mail and notify the 
postmas...@bl.uk : The contents of this e-mail must 
not be disclosed or copied without the sender's consent.
The statements and opinions expressed in this message are those of the author 
and do not necessarily reflect those of the British Library. The British 
Library does not take any responsibility for the views of the author.
*
Think before you print



--
Charlie Hull - Managing Consultant at OpenSource Connections Limited 

Founding member of The Search Network  
and co-author of Searching the Enterprise 


tel/fax: +44 (0)8700 118334
mobile: +44 (0)7767 825828

SOLR upgrade

[Paul, Lulu]

Hi SOLR team,

Please may I ask for advice regarding upgrading the SOLR version (our project 
currently running on solr-5.2.1) to the latest version?
What are the steps, breaking changes and potential issues ? Could this be done 
as an incremental version upgrade or a direct jump to the newest version?

Much appreciate the advice, Thank you!

Best Wishes
Lulu


**
Experience the British Library online at www.bl.uk
The British Library's latest Annual Report and Accounts : 
www.bl.uk/aboutus/annrep/index.html
Help the British Library conserve the world's knowledge. Adopt a Book. 
www.bl.uk/adoptabook
The Library's St Pancras site is WiFi - enabled
*
The information contained in this e-mail is confidential and may be legally 
privileged. It is intended for the addressee(s) only. If you are not the 
intended recipient, please delete this e-mail and notify the 
postmas...@bl.uk : The contents of this e-mail must 
not be disclosed or copied without the sender's consent.
The statements and opinions expressed in this message are those of the author 
and do not necessarily reflect those of the British Library. The British 
Library does not take any responsibility for the views of the author.
*
Think before you print

Re: Issue in Solr upgrade from 5.x to 8.x

[Erick Erickson]

Lucene has never really supported this migration path. There’s a whole long 
discussion of why, but basically you can’t upgrade an index with 100% fidelity 
because the original information isn’t there. Here’s the most succinct 
definition I’ve seen (from Robert Muir):

"I think the key issue here is Lucene is an index not a database. Because it is 
a lossy index and does not retain all of the user's data, its not possible to 
safely migrate some things automagically. In the norms case IndexWriter needs 
to re-analyze the text ("re-index") and compute stats to get back the value, so 
it can be re-encoded. The function is y = f(x) and if x is not available its 
not possible, so lucene can't do it.””

The Lucene devs make valiant efforts to keep indexes compatible across one 
major version, but have never made guarantees about two or more. Which brings 
me to IndexUpgraderTool. That simply rewrites the index in the current version 
format, essentially making index access more efficient. It does _not_ 
synthesize f(x) for the reason above.

Starting with 6.0, a marker was written into every segment identifying the 
version it was written. That marker is preserved through all segment merges and 
IndexUpgraderTool also preserves it. Starting with 8.0, if any segment has a 
marker earlier than 7.x (or not marked at all)the error you’re seeing is thrown.

So the short form is that you must re-index your data when upgrading whenever 
any part of your index was ever written by version X-2.

Best,
Erick

> On Aug 5, 2020, at 7:47 AM, Anchal Sharma2 - anchs...@in.ibm.com 
>  wrote:
> 
> Hi All,
> 
> 
> We are presently using solr 5.3.0 and planning to migrate to version 8.4.1 .I 
> tried using index upgrader for the same .
> 
> I am able to upgrade 5.3.0->6.6.6 and 6.6.6 to 7.7.3.But when I try upgrading 
> 7.7.3 index  to 8.4.1,I keep getting following error :
> 
> 
> This index was initially created with Lucene 6.x while the current version is 
> 8.4.1 and Lucene only supports reading the current and previous major 
> versions.. This version of Lucene only supports indexes created with release 
> 7.0 and later.
> 
> 
> Is there any workaround to do this ,without re-indexing?Any help/suggestions  
> would be much appreciated.
> 
> 
> Thanks
> 
> Anchal
> 

Issue in Solr upgrade from 5.x to 8.x

[Anchal Sharma2 - anchs...@in.ibm.com]

Hi All,


We are presently using solr 5.3.0 and planning to migrate to version 8.4.1 .I 
tried using index upgrader for the same .

I am able to upgrade 5.3.0->6.6.6 and 6.6.6 to 7.7.3.But when I try upgrading 
7.7.3 index  to 8.4.1,I keep getting following error :


This index was initially created with Lucene 6.x while the current version is 
8.4.1 and Lucene only supports reading the current and previous major 
versions.. This version of Lucene only supports indexes created with release 
7.0 and later.


Is there any workaround to do this ,without re-indexing?Any help/suggestions  
would be much appreciated.


Thanks

Anchal

Re: Solr Upgrade Issue

[Jan Høydahl]

Hi,

There is no enough information in your email for any of us to help you.
Sounds like your company has created some custom integrations and perhaps 
servlet filters.
We do not know anything about your custom «createcore» functionality, so we 
cannot know why it does not work.
I’d recommend you ask the architects in your company who set up these cusom 
components.
Or if you believe there is a Solr issue and you have a log message to share, we 
might be able to help.

Jan

> 26. jun. 2020 kl. 10:13 skrev Ashok Mahendran 
> :
> 
> Hi Team,
> 
> We are upgrading from Solr 7.5.0 version to 8.5.2 version.
> 
> We are doing custom /createcore functionality from our web application. In 
> 7.5.0 version we mentioned the that Filter in web.xml for create core and it 
> is working fine.
> 
> For 8.5.2 that customized create core filter not calling. Is there anything 
> we restricting in 8.5.2 version.
> 
> Please confirm
> 
> Regards,
> Ashokkumar M
> 
> [Aspire Systems]
> 
> This e-mail message and any attachments are for the sole use of the intended 
> recipient(s) and may contain proprietary, confidential, trade secret or 
> privileged information. Any unauthorized review, use, disclosure or 
> distribution is prohibited and may be a violation of law. If you are not the 
> intended recipient, please contact the sender by reply e-mail and destroy all 
> copies of the original message.

Solr Upgrade Issue

[Ashok Mahendran]

Hi Team,

We are upgrading from Solr 7.5.0 version to 8.5.2 version.

We are doing custom /createcore functionality from our web application. In 
7.5.0 version we mentioned the that Filter in web.xml for create core and it is 
working fine.

For 8.5.2 that customized create core filter not calling. Is there anything we 
restricting in 8.5.2 version.

Please confirm

Regards,
Ashokkumar M

[Aspire Systems]

This e-mail message and any attachments are for the sole use of the intended 
recipient(s) and may contain proprietary, confidential, trade secret or 
privileged information. Any unauthorized review, use, disclosure or 
distribution is prohibited and may be a violation of law. If you are not the 
intended recipient, please contact the sender by reply e-mail and destroy all 
copies of the original message.

Re: Solr Upgrade socketTimeout issue in 8.2

[kshitij tyagi]

rds,
kshitij

On Wed, Feb 19, 2020 at 6:18 PM Erick Erickson 
wrote:

> Yogesh:
>
> Please do not hijack threads. The original poster requested information
> about
> socket timeouts. True “upgrade” was mentioned, but it was a completely
> different issue.
>
> Kshitij:
>
> There’s not much information to go on here. It’s possible you were running
> close to the timeout limit before and “something” changed just enough
> to go over that limit.
>
> I’m a bit confused though, you talk about commands like reload while
> indexing.
> What _exactly_ are you trying to do? Details matter.
>
> One thing that did changes was “schemaless” became the default. This
> causes reloads when Solr is indexing docs and comes across fields
> for the first time. I personally don’t recommend “schemaless”, so what
> happens if you turn that off?
>
> If you’re manually sending reloads, you might try doing them async.
>
> That said, you must start from a fresh index with _no_ documents in it
> when you upgrade more than one major version. Did you start over?
>
> Best,
> Erick
>
> > On Feb 19, 2020, at 3:58 AM, kshitij tyagi 
> wrote:
> >
> > Hi,
> >
> > Any information on socket timeout issue when using collection apis? I am
> > observing increased response time when using Collection APis in upgraded
> > version
> >
> > On Wed, Feb 19, 2020 at 2:22 PM Jörn Franke 
> wrote:
> >
> >> Yes you need to reindex.
> >> Update solrconfig, schemas to leverage the later feature of the version
> >> (some datatypes are now more optimal others are deprecated.
> >>
> >> Update Solrconfig.xml and schema to leverage the latest  datatypes ,
> >> features etc..
> >>
> >> Create new collection based on newest config.
> >> Use your regular Index process to move documents to new collection.
> >>
> >> Check if new collection works and has expected performance.
> >>
> >> Delete old collection.
> >>
> >> Test before in a test environment and not in production!
> >>
> >>> Am 19.02.2020 um 09:46 schrieb Yogesh Chaudhari
> >> :
> >>>
> >>> Hi,
> >>>
> >>> Could you please share me the steps to upgrade SOlr?
> >>>
> >>> Now I am using Solr cloud 5.2.1 on production and wanted to upgrade to
> >> SOlr7.7.2. I am doing this in 2 spteps SOlr 5.2.1 to SOlr 6.6.6 then
> SOlr
> >> 7.7.2.
> >>>
> >>> I have upgraded to Solr but getting issue for indexing of old
> >> documents.  I am badly stuck get get old document in migrated solr
> version.
> >>>
> >>> Should I do the re-indexing? If yes can you please share the way to
> >> re-indexing?
> >>>
> >>> Can you please provide your inputs on this?
> >>>
> >>> Thanks,
> >>>
> >>> Yogesh Chaudhari
> >>>
> >>> -Original Message-
> >>> From: kshitij tyagi 
> >>> Sent: Wednesday, February 19, 2020 12:52 PM
> >>> To: solr-user@lucene.apache.org
> >>> Subject: Solr Upgrade socketTimeout issue in 8.2
> >>>
> >>> Hi,
> >>>
> >>> We have upgraded our solrCloud from version 6.6.0 to 8.2.0
> >>>
> >>> At the time of indexing intermittently we are observing socketTimeout
> >> exception when using Collection apis. example when we try reloading one
> of
> >> the collection using CloudSolrClient class.
> >>>
> >>> Is there any performance degradation in Solrcloud collection apis?
> >>>
> >>> logs:
> >>>
> >>> IOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@357] - caught
> >> end of stream exception
> >>>
> >>> EndOfStreamException: Unable to read additional data from client
> >> sessionid 0x2663e756d775747, likely client has closed socket
> >>>
> >>> at
> org.apache.zookeeper.server.NIOServerCnxn.doIO(NIOServerCnxn.java:228)
> >>>
> >>> at
> >>>
> >>
> org.apache.zookeeper.server.NIOServerCnxnFactory.run(NIOServerCnxnFactory.java:203)
> >>>
> >>> at java.lang.Thread.run(Unknown Source)
> >>>
> >>>
> >>> logs:
> >>>
> >>>
> >>> Exception has occured in job switch: Timeout occurred while waiting
> >> response from server at:
> >>
> http://secure-web.cisco.com/1w_RA10DqbruLQVC6aKUXuMgV4hC3T14viv2m2iUptQ2hyGjYLn0sSSy0Q_XNqcVxHym-e_mOyPc_AYM4zpIWWXdyRCpvXzL3mSeFK-DzhL_CqoNi2FwQUvhk2zb8OQKs1e11yBHqblc3Kyx0XlruLvb24BUj0lBBGmJVf5E9rrTaFQbFmCdNyccx1KCIpzf2MlyeqvvXVWKCW_YbqnLWGjcfqlAylbNqJTGuKf5rbBMdJ8pn14dbFlM0QDZjn6IORWVA8NqmdhC9VwD1rzpU6dVIpsph6qz_OcgoH61wlZALQ1Zj65XRFtXvuhqEWQeaabvKactprjz1o3pflKaxttbgxz1ItRxb4FjZkBgTC24uwalAmi_CyfeP7DECtIYATYf3AJFjCUfLV8_Rj2V5J0JeCTFDi7CWqKFUhiHXtpM8PvZt8kgMIRwfgPUKHPIJ/http%3A%2F%2Fprod-t-8.net%3A8983%2Fsolr
> >>>
> >>>
> >>> Is anyone facing same type of issue? in Solrcloud? Any suggestions to
> >> solve??
> >>>
> >>>
> >>>
> >>> Regards,
> >>>
> >>> kshitij
> >>
>
>

Re: Solr Upgrade socketTimeout issue in 8.2

[Erick Erickson]

Yogesh:

Please do not hijack threads. The original poster requested information about
socket timeouts. True “upgrade” was mentioned, but it was a completely
different issue.

Kshitij:

There’s not much information to go on here. It’s possible you were running
close to the timeout limit before and “something” changed just enough
to go over that limit.

I’m a bit confused though, you talk about commands like reload while indexing.
What _exactly_ are you trying to do? Details matter.

One thing that did changes was “schemaless” became the default. This
causes reloads when Solr is indexing docs and comes across fields
for the first time. I personally don’t recommend “schemaless”, so what
happens if you turn that off?

If you’re manually sending reloads, you might try doing them async.

That said, you must start from a fresh index with _no_ documents in it
when you upgrade more than one major version. Did you start over?

Best,
Erick

> On Feb 19, 2020, at 3:58 AM, kshitij tyagi  wrote:
> 
> Hi,
> 
> Any information on socket timeout issue when using collection apis? I am
> observing increased response time when using Collection APis in upgraded
> version
> 
> On Wed, Feb 19, 2020 at 2:22 PM Jörn Franke  wrote:
> 
>> Yes you need to reindex.
>> Update solrconfig, schemas to leverage the later feature of the version
>> (some datatypes are now more optimal others are deprecated.
>> 
>> Update Solrconfig.xml and schema to leverage the latest  datatypes ,
>> features etc..
>> 
>> Create new collection based on newest config.
>> Use your regular Index process to move documents to new collection.
>> 
>> Check if new collection works and has expected performance.
>> 
>> Delete old collection.
>> 
>> Test before in a test environment and not in production!
>> 
>>> Am 19.02.2020 um 09:46 schrieb Yogesh Chaudhari
>> :
>>> 
>>> Hi,
>>> 
>>> Could you please share me the steps to upgrade SOlr?
>>> 
>>> Now I am using Solr cloud 5.2.1 on production and wanted to upgrade to
>> SOlr7.7.2. I am doing this in 2 spteps SOlr 5.2.1 to SOlr 6.6.6 then SOlr
>> 7.7.2.
>>> 
>>> I have upgraded to Solr but getting issue for indexing of old
>> documents.  I am badly stuck get get old document in migrated solr version.
>>> 
>>> Should I do the re-indexing? If yes can you please share the way to
>> re-indexing?
>>> 
>>> Can you please provide your inputs on this?
>>> 
>>> Thanks,
>>> 
>>> Yogesh Chaudhari
>>> 
>>> -Original Message-
>>> From: kshitij tyagi 
>>> Sent: Wednesday, February 19, 2020 12:52 PM
>>> To: solr-user@lucene.apache.org
>>> Subject: Solr Upgrade socketTimeout issue in 8.2
>>> 
>>> Hi,
>>> 
>>> We have upgraded our solrCloud from version 6.6.0 to 8.2.0
>>> 
>>> At the time of indexing intermittently we are observing socketTimeout
>> exception when using Collection apis. example when we try reloading one of
>> the collection using CloudSolrClient class.
>>> 
>>> Is there any performance degradation in Solrcloud collection apis?
>>> 
>>> logs:
>>> 
>>> IOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@357] - caught
>> end of stream exception
>>> 
>>> EndOfStreamException: Unable to read additional data from client
>> sessionid 0x2663e756d775747, likely client has closed socket
>>> 
>>> at org.apache.zookeeper.server.NIOServerCnxn.doIO(NIOServerCnxn.java:228)
>>> 
>>> at
>>> 
>> org.apache.zookeeper.server.NIOServerCnxnFactory.run(NIOServerCnxnFactory.java:203)
>>> 
>>> at java.lang.Thread.run(Unknown Source)
>>> 
>>> 
>>> logs:
>>> 
>>> 
>>> Exception has occured in job switch: Timeout occurred while waiting
>> response from server at:
>> http://secure-web.cisco.com/1w_RA10DqbruLQVC6aKUXuMgV4hC3T14viv2m2iUptQ2hyGjYLn0sSSy0Q_XNqcVxHym-e_mOyPc_AYM4zpIWWXdyRCpvXzL3mSeFK-DzhL_CqoNi2FwQUvhk2zb8OQKs1e11yBHqblc3Kyx0XlruLvb24BUj0lBBGmJVf5E9rrTaFQbFmCdNyccx1KCIpzf2MlyeqvvXVWKCW_YbqnLWGjcfqlAylbNqJTGuKf5rbBMdJ8pn14dbFlM0QDZjn6IORWVA8NqmdhC9VwD1rzpU6dVIpsph6qz_OcgoH61wlZALQ1Zj65XRFtXvuhqEWQeaabvKactprjz1o3pflKaxttbgxz1ItRxb4FjZkBgTC24uwalAmi_CyfeP7DECtIYATYf3AJFjCUfLV8_Rj2V5J0JeCTFDi7CWqKFUhiHXtpM8PvZt8kgMIRwfgPUKHPIJ/http%3A%2F%2Fprod-t-8.net%3A8983%2Fsolr
>>> 
>>> 
>>> Is anyone facing same type of issue? in Solrcloud? Any suggestions to
>> solve??
>>> 
>>> 
>>> 
>>> Regards,
>>> 
>>> kshitij
>> 

Re: Solr Upgrade socketTimeout issue in 8.2

[kshitij tyagi]

Hi,

Any information on socket timeout issue when using collection apis? I am
observing increased response time when using Collection APis in upgraded
version

On Wed, Feb 19, 2020 at 2:22 PM Jörn Franke  wrote:

> Yes you need to reindex.
> Update solrconfig, schemas to leverage the later feature of the version
> (some datatypes are now more optimal others are deprecated.
>
> Update Solrconfig.xml and schema to leverage the latest  datatypes ,
> features etc..
>
> Create new collection based on newest config.
> Use your regular Index process to move documents to new collection.
>
> Check if new collection works and has expected performance.
>
> Delete old collection.
>
> Test before in a test environment and not in production!
>
> > Am 19.02.2020 um 09:46 schrieb Yogesh Chaudhari
> :
> >
> > Hi,
> >
> > Could you please share me the steps to upgrade SOlr?
> >
> > Now I am using Solr cloud 5.2.1 on production and wanted to upgrade to
> SOlr7.7.2. I am doing this in 2 spteps SOlr 5.2.1 to SOlr 6.6.6 then SOlr
> 7.7.2.
> >
> > I have upgraded to Solr but getting issue for indexing of old
> documents.  I am badly stuck get get old document in migrated solr version.
> >
> > Should I do the re-indexing? If yes can you please share the way to
> re-indexing?
> >
> > Can you please provide your inputs on this?
> >
> > Thanks,
> >
> > Yogesh Chaudhari
> >
> > -Original Message-
> > From: kshitij tyagi 
> > Sent: Wednesday, February 19, 2020 12:52 PM
> > To: solr-user@lucene.apache.org
> > Subject: Solr Upgrade socketTimeout issue in 8.2
> >
> > Hi,
> >
> > We have upgraded our solrCloud from version 6.6.0 to 8.2.0
> >
> > At the time of indexing intermittently we are observing socketTimeout
> exception when using Collection apis. example when we try reloading one of
> the collection using CloudSolrClient class.
> >
> > Is there any performance degradation in Solrcloud collection apis?
> >
> > logs:
> >
> > IOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@357] - caught
> end of stream exception
> >
> > EndOfStreamException: Unable to read additional data from client
> sessionid 0x2663e756d775747, likely client has closed socket
> >
> > at org.apache.zookeeper.server.NIOServerCnxn.doIO(NIOServerCnxn.java:228)
> >
> > at
> >
> org.apache.zookeeper.server.NIOServerCnxnFactory.run(NIOServerCnxnFactory.java:203)
> >
> > at java.lang.Thread.run(Unknown Source)
> >
> >
> > logs:
> >
> >
> > Exception has occured in job switch: Timeout occurred while waiting
> response from server at:
> http://secure-web.cisco.com/1w_RA10DqbruLQVC6aKUXuMgV4hC3T14viv2m2iUptQ2hyGjYLn0sSSy0Q_XNqcVxHym-e_mOyPc_AYM4zpIWWXdyRCpvXzL3mSeFK-DzhL_CqoNi2FwQUvhk2zb8OQKs1e11yBHqblc3Kyx0XlruLvb24BUj0lBBGmJVf5E9rrTaFQbFmCdNyccx1KCIpzf2MlyeqvvXVWKCW_YbqnLWGjcfqlAylbNqJTGuKf5rbBMdJ8pn14dbFlM0QDZjn6IORWVA8NqmdhC9VwD1rzpU6dVIpsph6qz_OcgoH61wlZALQ1Zj65XRFtXvuhqEWQeaabvKactprjz1o3pflKaxttbgxz1ItRxb4FjZkBgTC24uwalAmi_CyfeP7DECtIYATYf3AJFjCUfLV8_Rj2V5J0JeCTFDi7CWqKFUhiHXtpM8PvZt8kgMIRwfgPUKHPIJ/http%3A%2F%2Fprod-t-8.net%3A8983%2Fsolr
> >
> >
> > Is anyone facing same type of issue? in Solrcloud? Any suggestions to
> solve??
> >
> >
> >
> > Regards,
> >
> > kshitij
>

Re: Solr Upgrade socketTimeout issue in 8.2

[Jörn Franke]

Yes you need to reindex.
Update solrconfig, schemas to leverage the later feature of the version (some 
datatypes are now more optimal others are deprecated.

Update Solrconfig.xml and schema to leverage the latest  datatypes , features 
etc..

Create new collection based on newest config.
Use your regular Index process to move documents to new collection.

Check if new collection works and has expected performance.

Delete old collection.

Test before in a test environment and not in production!

> Am 19.02.2020 um 09:46 schrieb Yogesh Chaudhari 
> :
> 
> Hi,
> 
> Could you please share me the steps to upgrade SOlr?
> 
> Now I am using Solr cloud 5.2.1 on production and wanted to upgrade to 
> SOlr7.7.2. I am doing this in 2 spteps SOlr 5.2.1 to SOlr 6.6.6 then SOlr 
> 7.7.2.
> 
> I have upgraded to Solr but getting issue for indexing of old documents.  I 
> am badly stuck get get old document in migrated solr version.
> 
> Should I do the re-indexing? If yes can you please share the way to 
> re-indexing?
> 
> Can you please provide your inputs on this? 
> 
> Thanks,
> 
> Yogesh Chaudhari
> 
> -Original Message-
> From: kshitij tyagi  
> Sent: Wednesday, February 19, 2020 12:52 PM
> To: solr-user@lucene.apache.org
> Subject: Solr Upgrade socketTimeout issue in 8.2
> 
> Hi,
> 
> We have upgraded our solrCloud from version 6.6.0 to 8.2.0
> 
> At the time of indexing intermittently we are observing socketTimeout 
> exception when using Collection apis. example when we try reloading one of 
> the collection using CloudSolrClient class.
> 
> Is there any performance degradation in Solrcloud collection apis?
> 
> logs:
> 
> IOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@357] - caught end of 
> stream exception
> 
> EndOfStreamException: Unable to read additional data from client sessionid 
> 0x2663e756d775747, likely client has closed socket
> 
> at org.apache.zookeeper.server.NIOServerCnxn.doIO(NIOServerCnxn.java:228)
> 
> at
> org.apache.zookeeper.server.NIOServerCnxnFactory.run(NIOServerCnxnFactory.java:203)
> 
> at java.lang.Thread.run(Unknown Source)
> 
> 
> logs:
> 
> 
> Exception has occured in job switch: Timeout occurred while waiting response 
> from server 
> at:http://secure-web.cisco.com/1w_RA10DqbruLQVC6aKUXuMgV4hC3T14viv2m2iUptQ2hyGjYLn0sSSy0Q_XNqcVxHym-e_mOyPc_AYM4zpIWWXdyRCpvXzL3mSeFK-DzhL_CqoNi2FwQUvhk2zb8OQKs1e11yBHqblc3Kyx0XlruLvb24BUj0lBBGmJVf5E9rrTaFQbFmCdNyccx1KCIpzf2MlyeqvvXVWKCW_YbqnLWGjcfqlAylbNqJTGuKf5rbBMdJ8pn14dbFlM0QDZjn6IORWVA8NqmdhC9VwD1rzpU6dVIpsph6qz_OcgoH61wlZALQ1Zj65XRFtXvuhqEWQeaabvKactprjz1o3pflKaxttbgxz1ItRxb4FjZkBgTC24uwalAmi_CyfeP7DECtIYATYf3AJFjCUfLV8_Rj2V5J0JeCTFDi7CWqKFUhiHXtpM8PvZt8kgMIRwfgPUKHPIJ/http%3A%2F%2Fprod-t-8.net%3A8983%2Fsolr
> 
> 
> Is anyone facing same type of issue? in Solrcloud? Any suggestions to solve??
> 
> 
> 
> Regards,
> 
> kshitij

RE: Solr Upgrade socketTimeout issue in 8.2

[Yogesh Chaudhari]

Hi,

Could you please share me the steps to upgrade SOlr?

Now I am using Solr cloud 5.2.1 on production and wanted to upgrade to 
SOlr7.7.2. I am doing this in 2 spteps SOlr 5.2.1 to SOlr 6.6.6 then SOlr 7.7.2.

I have upgraded to Solr but getting issue for indexing of old documents.  I am 
badly stuck get get old document in migrated solr version.

Should I do the re-indexing? If yes can you please share the way to re-indexing?

Can you please provide your inputs on this? 

Thanks,

Yogesh Chaudhari

-Original Message-
From: kshitij tyagi  
Sent: Wednesday, February 19, 2020 12:52 PM
To: solr-user@lucene.apache.org
Subject: Solr Upgrade socketTimeout issue in 8.2

Hi,

We have upgraded our solrCloud from version 6.6.0 to 8.2.0

At the time of indexing intermittently we are observing socketTimeout exception 
when using Collection apis. example when we try reloading one of the collection 
using CloudSolrClient class.

Is there any performance degradation in Solrcloud collection apis?

logs:

IOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@357] - caught end of 
stream exception

EndOfStreamException: Unable to read additional data from client sessionid 
0x2663e756d775747, likely client has closed socket

at org.apache.zookeeper.server.NIOServerCnxn.doIO(NIOServerCnxn.java:228)

at
org.apache.zookeeper.server.NIOServerCnxnFactory.run(NIOServerCnxnFactory.java:203)

at java.lang.Thread.run(Unknown Source)


logs:


Exception has occured in job switch: Timeout occurred while waiting response 
from server 
at:http://secure-web.cisco.com/1w_RA10DqbruLQVC6aKUXuMgV4hC3T14viv2m2iUptQ2hyGjYLn0sSSy0Q_XNqcVxHym-e_mOyPc_AYM4zpIWWXdyRCpvXzL3mSeFK-DzhL_CqoNi2FwQUvhk2zb8OQKs1e11yBHqblc3Kyx0XlruLvb24BUj0lBBGmJVf5E9rrTaFQbFmCdNyccx1KCIpzf2MlyeqvvXVWKCW_YbqnLWGjcfqlAylbNqJTGuKf5rbBMdJ8pn14dbFlM0QDZjn6IORWVA8NqmdhC9VwD1rzpU6dVIpsph6qz_OcgoH61wlZALQ1Zj65XRFtXvuhqEWQeaabvKactprjz1o3pflKaxttbgxz1ItRxb4FjZkBgTC24uwalAmi_CyfeP7DECtIYATYf3AJFjCUfLV8_Rj2V5J0JeCTFDi7CWqKFUhiHXtpM8PvZt8kgMIRwfgPUKHPIJ/http%3A%2F%2Fprod-t-8.net%3A8983%2Fsolr


Is anyone facing same type of issue? in Solrcloud? Any suggestions to solve??



Regards,

kshitij

Solr Upgrade socketTimeout issue in 8.2

[kshitij tyagi]

Hi,

We have upgraded our solrCloud from version 6.6.0 to 8.2.0

At the time of indexing intermittently we are observing socketTimeout
exception when using Collection apis. example when we try reloading one of
the collection using CloudSolrClient class.

Is there any performance degradation in Solrcloud collection apis?

logs:

IOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@357] - caught end of
stream exception

EndOfStreamException: Unable to read additional data from client sessionid
0x2663e756d775747, likely client has closed socket

at org.apache.zookeeper.server.NIOServerCnxn.doIO(NIOServerCnxn.java:228)

at
org.apache.zookeeper.server.NIOServerCnxnFactory.run(NIOServerCnxnFactory.java:203)

at java.lang.Thread.run(Unknown Source)


logs:


Exception has occured in job switch: Timeout occurred while waiting
response from server at:http://prod-t-8.net:8983/solr


Is anyone facing same type of issue? in Solrcloud? Any suggestions to solve??



Regards,

kshitij

Re: Zookeeper upgrade required with Solr upgrade?

[Erick Erickson]

Yeah, 3.4.x upgrades were pretty strainght-forward.

The 3.5.5 upgrade was trickier, but the problems were in the
admin UI. The admin UI uses several “4 letter words” to do its
ZooKeeper reporting, and that required explicit permissions, but IIRC
that all only affected the admin UI reporting about Zookeeper. There
were a _lot_ of Solr changes, but that was mostly cosmetic and mostly
in the test code.

Best,
Erick

> On Feb 13, 2020, at 4:07 PM, Rahul Goswami  wrote:
> 
> Thanks Eric. Also, thanks for that little pointer about the JIRA. Just to
> make sure I also checked for the upgrade JIRAs for other two intermediate
> Zookeeper versions 3.4.11 and 3.4.13 between Solr 7.2.1 and Solr 7.7.2 and
> they didn't seem to contain any Solr code changes either.
> 
> On Thu, Feb 13, 2020 at 9:26 AM Erick Erickson 
> wrote:
> 
>> That should be OK. There were no code changes necessary for that upgrade.
>> see SOLR-13363
>> 
>>> On Feb 12, 2020, at 5:34 PM, Rahul Goswami 
>> wrote:
>>> 
>>> Hello,
>>> We are running a SolrCloud (7.2.1) cluster and upgrading to Solr 7.7.2.
>> We
>>> run a separate multi node zookeeper ensemble which currently runs
>>> Zookeeper 3.4.10.
>>> Is it also required to upgrade Zookeeper (to  3.4.14 as per change.txt
>> for
>>> Solr 7.7.2) along with Solr ?
>>> 
>>> I tried a few basic updates requests for a 2 node SolrCloud cluster with
>>> the older (3.4.10) zookeeper and it seemed to work fine. But just want to
>>> know if there are any caveats I should be aware of.
>>> 
>>> Thanks,
>>> Rahul
>> 
>> 

Re: Zookeeper upgrade required with Solr upgrade?

[Rahul Goswami]

Thanks Eric. Also, thanks for that little pointer about the JIRA. Just to
make sure I also checked for the upgrade JIRAs for other two intermediate
Zookeeper versions 3.4.11 and 3.4.13 between Solr 7.2.1 and Solr 7.7.2 and
they didn't seem to contain any Solr code changes either.

On Thu, Feb 13, 2020 at 9:26 AM Erick Erickson 
wrote:

> That should be OK. There were no code changes necessary for that upgrade.
> see SOLR-13363
>
> > On Feb 12, 2020, at 5:34 PM, Rahul Goswami 
> wrote:
> >
> > Hello,
> > We are running a SolrCloud (7.2.1) cluster and upgrading to Solr 7.7.2.
> We
> > run a separate multi node zookeeper ensemble which currently runs
> > Zookeeper 3.4.10.
> > Is it also required to upgrade Zookeeper (to  3.4.14 as per change.txt
> for
> > Solr 7.7.2) along with Solr ?
> >
> > I tried a few basic updates requests for a 2 node SolrCloud cluster with
> > the older (3.4.10) zookeeper and it seemed to work fine. But just want to
> > know if there are any caveats I should be aware of.
> >
> > Thanks,
> > Rahul
>
>

Re: Zookeeper upgrade required with Solr upgrade?

[Erick Erickson]

That should be OK. There were no code changes necessary for that upgrade. see 
SOLR-13363

> On Feb 12, 2020, at 5:34 PM, Rahul Goswami  wrote:
> 
> Hello,
> We are running a SolrCloud (7.2.1) cluster and upgrading to Solr 7.7.2. We
> run a separate multi node zookeeper ensemble which currently runs
> Zookeeper 3.4.10.
> Is it also required to upgrade Zookeeper (to  3.4.14 as per change.txt for
> Solr 7.7.2) along with Solr ?
> 
> I tried a few basic updates requests for a 2 node SolrCloud cluster with
> the older (3.4.10) zookeeper and it seemed to work fine. But just want to
> know if there are any caveats I should be aware of.
> 
> Thanks,
> Rahul

Zookeeper upgrade required with Solr upgrade?

[Rahul Goswami]

Hello,
We are running a SolrCloud (7.2.1) cluster and upgrading to Solr 7.7.2. We
run a separate multi node zookeeper ensemble which currently runs
Zookeeper 3.4.10.
Is it also required to upgrade Zookeeper (to  3.4.14 as per change.txt for
Solr 7.7.2) along with Solr ?

I tried a few basic updates requests for a 2 node SolrCloud cluster with
the older (3.4.10) zookeeper and it seemed to work fine. But just want to
know if there are any caveats I should be aware of.

Thanks,
Rahul

RE: Solr upgrade question

[Margo Breäs | INDI]

Erick and Charlie, thanks for your responses. It's clear that it is better to 
read the CHANGES.txt files first and then decide in how many steps the upgrade 
should take place.

Best, Margo





Met vriendelijke groet / Kind regards,
Margo Breäs
​Categoriespecialist
​T. +31 88 0666 000
​E. margo.br...@indi.nl
​W. www.indi.nl
-Original Message-
From: Erick Erickson 
Sent: vrijdag 5 juli 2019 17:37
To: solr-user@lucene.apache.org
Subject: Re: Solr upgrade question

There are a _lot_ of changes since 4.8.1.

1> plan on re-indexing the entire corpus. This is required when jumping more 
than one major version.

2> Treat it as a green-field application. In particular do not just copy your 
schema and config files into 8x and start running. Instead, identify any 
changes you made to 4.8.1 and make similar changes to the stock 8x configs.

3> Really read the CHANGES.txt files for both Lucene and Solr. It’ll be mind 
numbing, but you can get a good sense of the changes that affect upgrading by 
reading the “upgrade notes” for each release between 4.8.1 and the current 
version you settle on.

If the upgrade notes generate specific questions, don’t hesitate to ask.

Best,
Erick

> On Jul 5, 2019, at 6:49 AM, Margo Breäs | INDI  wrote:
>
> Hi all,
>
> At the moment we are working with Solr version 4.8.1 in combination with an 
> older version of Intershop.
> We have recently migrated our entire shop to a new party, and so there is 
> room for improvements.
>
> Are there any known issues with upgrading over that many versions in general, 
> or with an Intershop version specifically?
> If so we would appreciate your experiences/stories, so we can mitigate things 
> beforehand.
>
> Thanks in advance,
>
> best regards,
>
> Margo Breas | INDI
>
>
>
> Met vriendelijke groet / Kind regards,​
>
> Margo Breäs
> ​Categoriespecialist
> ​T. +31 88 0666 000
> ​E. margo.br...@indi.nl
> ​W. www.indi.nl

Re: Solr upgrade question

[Charlie Hull]

On 05/07/2019 14:49, Margo Breäs | INDI wrote:


Hi all,

At the moment we are working with Solr version 4.8.1 in combination 
with an older version of Intershop.


We have recently migrated our entire shop to a new party, and so there 
is room for improvements.


Are there any known issues with upgrading over that many versions in 
general, or with an Intershop version specifically?


If so we would appreciate your experiences/stories, so we can mitigate 
things beforehand.


If you're going to migrate from that old a version of Solr, I think you 
will need to re-index completely and also check that all your queries 
work as you expect...there have been a lot of changes since then and 
don't underestimate the task!


Cheers


Charlie


Thanks in advance,

best regards,

Margo Breas | INDI


Met vriendelijke groet / Kind regards,​


Margo Breäs
​Categoriespecialist
​T. +31 88 0666 000
​E. *margo.br...@indi.nl* 
*​W. www.indi.nl* 
 



INDI.nl website 
 





--
Charlie Hull
Flax - Open Source Enterprise Search

tel/fax: +44 (0)8700 118334
mobile:  +44 (0)7767 825828
web: www.flax.co.uk

Re: Solr upgrade question

[Erick Erickson]

There are a _lot_ of changes since 4.8.1. 

1> plan on re-indexing the entire corpus. This is required when jumping more 
than one major version.

2> Treat it as a green-field application. In particular do not just copy your 
schema and config files into 8x and start running. Instead, identify any 
changes you made to 4.8.1 and make similar changes to the stock 8x configs.

3> Really read the CHANGES.txt files for both Lucene and Solr. It’ll be mind 
numbing, but you can get a good sense of the changes that affect upgrading by 
reading the “upgrade notes” for each release between 4.8.1 and the current 
version you settle on.

If the upgrade notes generate specific questions, don’t hesitate to ask.

Best,
Erick

> On Jul 5, 2019, at 6:49 AM, Margo Breäs | INDI  wrote:
> 
> Hi all,
>  
> At the moment we are working with Solr version 4.8.1 in combination with an 
> older version of Intershop.
> We have recently migrated our entire shop to a new party, and so there is 
> room for improvements.
>  
> Are there any known issues with upgrading over that many versions in general, 
> or with an Intershop version specifically?
> If so we would appreciate your experiences/stories, so we can mitigate things 
> beforehand.
>  
> Thanks in advance,
>  
> best regards,
>  
> Margo Breas | INDI
>  
>  
> 
> Met vriendelijke groet / Kind regards,​
> 
> Margo Breäs
> ​Categoriespecialist 
> ​T. +31 88 0666 000 
> ​E. margo.br...@indi.nl 
> ​W. www.indi.nl

Solr upgrade question

[Margo Breäs | INDI]

Hi all,

At the moment we are working with Solr version 4.8.1 in combination with an 
older version of Intershop.
We have recently migrated our entire shop to a new party, and so there is room 
for improvements.

Are there any known issues with upgrading over that many versions in general, 
or with an Intershop version specifically?
If so we would appreciate your experiences/stories, so we can mitigate things 
beforehand.

Thanks in advance,

best regards,

Margo Breas | INDI




Met vriendelijke groet / Kind regards,
Margo Breäs
​Categoriespecialist
​T. +31 88 0666 000
​E. margo.br...@indi.nl
​W. www.indi.nl

Re: migrating cores with Solr upgrade

[Erick Erickson]

Oops fumble fingers. Anyway I'd recommend completely reindexing into a new
collection.

On Sun, Nov 4, 2018, 12:53 Erick Erickson  Lucene does not guarantee back comparability over two major versions, so
> I'd recommend completely reinde
>
> On Sun, Nov 4, 2018, 02:02 Piyush Kumar Nayak  wrote:
>
>> Hi,
>>
>> What is the best way to migrate cores from an old version of Solr (say
>> 5.x) to a newer version (say 7.x). I did not find anything pertinent to the
>> matter in the Solr reference guide.
>> Is there a tool that can do that seamlessly?
>>
>> Regards,
>> Piyush.
>>
>>

Re: migrating cores with Solr upgrade

[Erick Erickson]

Lucene does not guarantee back comparability over two major versions, so
I'd recommend completely reinde

On Sun, Nov 4, 2018, 02:02 Piyush Kumar Nayak  Hi,
>
> What is the best way to migrate cores from an old version of Solr (say
> 5.x) to a newer version (say 7.x). I did not find anything pertinent to the
> matter in the Solr reference guide.
> Is there a tool that can do that seamlessly?
>
> Regards,
> Piyush.
>
>

migrating cores with Solr upgrade

[Piyush Kumar Nayak]

Hi,

What is the best way to migrate cores from an old version of Solr (say 5.x) to 
a newer version (say 7.x). I did not find anything pertinent to the matter in 
the Solr reference guide.
Is there a tool that can do that seamlessly?

Regards,
Piyush.

Re: Apache SOLR upgrade from 5.2.1 to 7.x

[Erick Erickson]

IIUC the 5x->7x upgrade won't immediately fail like a 6x->8x upgrade
would, but neither is it really expected to produce the results you
expect due to differences in the index formats.
On Sat, Oct 6, 2018 at 1:31 PM Jan Høydahl  wrote:
>
> Shawn, my impression is that you WILL be able to upgrade a 5.x index to 6.x 
> and then to 7.x for use with 7.x. So your wiki page is a bit too strict here.
> But if you ever want to upgrade to 8.x, that version will require the "first 
> created" version to be 7.0 or later, so you'll need a full reindex.
> See SOLR-12281 .
>
> I'd also recommend to plan for a full re-index, and also upgrade to new field 
> types etc at the same time.
> Feel free to give this tool 
> https://github.com/cominvent/solr-tools/tree/master/upgradeindex 
>  a spin in 
> your test environtment and then just test whether 7.5 works on that index :)
>
> --
> Jan Høydahl, search solution architect
> Cominvent AS - www.cominvent.com
>
> > 5. okt. 2018 kl. 16:49 skrev Shawn Heisey :
> >
> > On 10/5/2018 4:41 AM, padmanabhan1616 wrote:
> >> 1. We cannot upgrade directly from 5.x to 7.x instead upgrade to 5.5 then
> >> upgrade to 7 as there is major index format level changes taken place in 
> >> 5.5
> >> or later version.
> >
> > Solr 7.x cannot read indexes from 5.5.  It can only read indexes that were 
> > *fully* constructed by versions back to 6.0.0.
> >
> >> 1. Use index upgrade tool which can allow to upgrade all old indexes to new
> >> index format then we can upgrade to 7.x version easily.
> >
> > We have been advised by Lucene experts that if a version that's at least 
> > two major versions before the target version has *EVER* touched the index, 
> > there's no guarantee that the index will work even after upgrading through 
> > the major versions one by one. The compatibility guarantee only goes back 
> > one major version.
> >
> > I would strongly recommend with ANY upgrade that you always build the index 
> > from scratch.  That produces the best results.
> >
> > This is becoming a frequently asked question, so I have built a wiki page 
> > to answer it:
> >
> > https://wiki.apache.org/solr/VersionCompatibility
> >
> > Thanks,
> > Shawn
> >
>

Re: Apache SOLR upgrade from 5.2.1 to 7.x

[Jan Høydahl]

Shawn, my impression is that you WILL be able to upgrade a 5.x index to 6.x and 
then to 7.x for use with 7.x. So your wiki page is a bit too strict here.
But if you ever want to upgrade to 8.x, that version will require the "first 
created" version to be 7.0 or later, so you'll need a full reindex.
See SOLR-12281 .

I'd also recommend to plan for a full re-index, and also upgrade to new field 
types etc at the same time.
Feel free to give this tool 
https://github.com/cominvent/solr-tools/tree/master/upgradeindex 
 a spin in 
your test environtment and then just test whether 7.5 works on that index :)

--
Jan Høydahl, search solution architect
Cominvent AS - www.cominvent.com

> 5. okt. 2018 kl. 16:49 skrev Shawn Heisey :
> 
> On 10/5/2018 4:41 AM, padmanabhan1616 wrote:
>> 1. We cannot upgrade directly from 5.x to 7.x instead upgrade to 5.5 then
>> upgrade to 7 as there is major index format level changes taken place in 5.5
>> or later version.
> 
> Solr 7.x cannot read indexes from 5.5.  It can only read indexes that were 
> *fully* constructed by versions back to 6.0.0.
> 
>> 1. Use index upgrade tool which can allow to upgrade all old indexes to new
>> index format then we can upgrade to 7.x version easily.
> 
> We have been advised by Lucene experts that if a version that's at least two 
> major versions before the target version has *EVER* touched the index, 
> there's no guarantee that the index will work even after upgrading through 
> the major versions one by one. The compatibility guarantee only goes back one 
> major version.
> 
> I would strongly recommend with ANY upgrade that you always build the index 
> from scratch.  That produces the best results.
> 
> This is becoming a frequently asked question, so I have built a wiki page to 
> answer it:
> 
> https://wiki.apache.org/solr/VersionCompatibility
> 
> Thanks,
> Shawn
> 

Re: Apache SOLR upgrade from 5.2.1 to 7.x

[Shawn Heisey]

On 10/5/2018 4:41 AM, padmanabhan1616 wrote:

1. We cannot upgrade directly from 5.x to 7.x instead upgrade to 5.5 then
upgrade to 7 as there is major index format level changes taken place in 5.5
or later version.


Solr 7.x cannot read indexes from 5.5.  It can only read indexes that 
were *fully* constructed by versions back to 6.0.0.



1. Use index upgrade tool which can allow to upgrade all old indexes to new
index format then we can upgrade to 7.x version easily.


We have been advised by Lucene experts that if a version that's at least 
two major versions before the target version has *EVER* touched the 
index, there's no guarantee that the index will work even after 
upgrading through the major versions one by one. The compatibility 
guarantee only goes back one major version.


I would strongly recommend with ANY upgrade that you always build the 
index from scratch.  That produces the best results.


This is becoming a frequently asked question, so I have built a wiki 
page to answer it:


https://wiki.apache.org/solr/VersionCompatibility

Thanks,
Shawn

Apache SOLR upgrade from 5.2.1 to 7.x

[padmanabhan1616]

Hi Team,

We planning to upgrade SOLR from 5.2.1 to 7.x version. I just googled and
found that there is no way of upgrading from 5.x to 7.x directly 

Here are the list of suggestions gathered from different sources

1. We cannot upgrade directly from 5.x to 7.x instead upgrade to 5.5 then
upgrade to 7 as there is major index format level changes taken place in 5.5
or later version.
1. Use index upgrade tool which can allow to upgrade all old indexes to new
index format then we can upgrade to 7.x version easily.

We are really struggling to get the right options here for this upgrade. 

I Know we are running very old version. We need this to be happen ASAP. 

Can you please suggest us what is the right approcuh here to upgrade from
5.2.1 version to 7.x version.

Thanks,
Padmanabhan



--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Solr upgrade issues

[Srinivas Kashyap]

Hi,

We are in the process of upgrading Solr from solr 5.2.1 to solr 7.4.0 and I'm 
facing below issues. Please help me in resolving.

1)HttpSolrClient tempClient = new 
HttpSolrClient.Builder("http://localhost:8983/solr";).build();

ModifiableSolrParams params = new 
ModifiableSolrParams();
   params.set("qt", "/dataimport");
   params.set("command", "delta-import");
   params.set("clean", "false");
   params.set("commit", "true");
   params.set("entity", "collection1");

GenericSolrRequest req = new 
GenericSolrRequest(SolrRequest.METHOD.POST, "/select" ,params);
   tempClient.request(req," collection1");


In the back end I have schedulers which call delta-import on my collection1. 
This used to work before in 5.2.1 and when this code gets executed, I could see 
the delta-import was being run. Now in 7.4.0, I'm not able to see the 
delta-import running. Does solr restricts taking external requests in 7.4.0?

2) Also in Jetty.xml , I have configured the datasource as below


  
 java:comp/env/jdbc/tssindex
 
 
 thin
 jdbc:oracle:thin:@localhost:1521:xe
 X
 X
 
 
 

How to fetch the data source configured in this xml 
(java:comp/env/jdbc/tssindex)

Earlier I used to fetch from tomcat context xml as below:

Context initContext = new InitialContext();
DataSource ds = null;
Context webContext = 
(Context)initContext.lookup("java:/comp/env");
ds = (DataSource) webContext.lookup("jdbc/tssindex");

How to fetch it in jetty.

Thanks in advance,
Srinivas kashyap

Re: Solr Upgrade DateField to TrieDateField

[Shawn Heisey]

On 6/20/2018 12:35 PM, Yunee Lee wrote:
> I have  two questions.
>
> 1. solr index on verion 4.6.0 and there are multiple date fields as the type 
> DateField in schema.xml
> When I upgraded to version 5.2.1 with new data type Trie* for integer, float, 
> string and date.
> Only date fields are not upgraded properly with  the following error.
> "trace": "java.lang.ClassCastException: java.lang.String cannot be cast 
> to java.util.Date\n\tat 



> 2. I also ran the Index upgrader then the core is Not registering correctly 
> with 
> "msg": "java.lang.String cannot be cast to java.util.Date"
>
> Is there any solutions with config changes without reindexing entire 
> documents?

If you change the type on ANY field, you have to reindex, and it's
typically best to build the entire index again from scratch.  There are
no tricks to avoid reindexing when changing your schema.

https://wiki.apache.org/solr/HowToReindex

Here's a four year old thread from this mailing list that might be relevant:

http://lucene.472066.n3.nabble.com/Trouble-with-TrieDateFields-td4143082.html

Thanks,
Shawn

Solr Upgrade DateField to TrieDateField

[Yunee Lee]

 Hi, 
Hi,
I have  two questions.

1. solr index on verion 4.6.0 and there are multiple date fields as the type 
DateField in schema.xml
When I upgraded to version 5.2.1 with new data type Trie* for integer, float, 
string and date.
Only date fields are not upgraded properly with  the following error.
"trace": "java.lang.ClassCastException: java.lang.String cannot be cast to 
java.util.Date\n\tat 
org.apache.solr.schema.TrieDateField.toObject(TrieDateField.java:337)\n\tat 
org.apache.solr.schema.TrieDateField.toObject(TrieDateField.java:102)\n\tat 
org.apache.solr.schema.TrieField.write(TrieField.java:256)\n\tat 
org.apache.solr.response.TextResponseWriter.writeVal(TextResponseWriter.java:131)\n\tat
 
org.apache.solr.response.JSONWriter.writeSolrDocument(JSONResponseWriter.java:356)\n\tat
 
org.apache.solr.response.TextResponseWriter.writeDocuments(TextResponseWriter.java:263)\n\tat
 
org.apache.solr.response.TextResponseWriter.writeVal(TextResponseWriter.java:173)\n\tat
 
org.apache.solr.response.JSONWriter.writeNamedListAsMapWithDups(JSONResponseWriter.java:184)\n\tat
 
org.apache.solr.response.JSONWriter.writeNamedList(JSONResponseWriter.java:300)\n\tat
 
org.apache.solr.response.JSONWriter.writeResponse(JSONResponseWriter.java:96)\n\tat
 
org.apache.solr.response.JSONResponseWriter.write(JSONResponseWriter.java:61)\n\tat
 
org.apache.solr.response.QueryResponseWriterUtil.writeQueryResponse(QueryResponseWriterUtil.java:53)\n\tat
 
org.apache.solr.servlet.HttpSolrCall.writeResponse(HttpSolrCall.java:727)\n\tat 
org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:459)\n\tat 
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:227)\n\tat
 
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:196)\n\tat
 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)\n\tat
 
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585)\n\tat
 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)\n\tat
 
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577)\n\tat
 
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223)\n\tat
 
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)\n\tat
 
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)\n\tat 
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)\n\tat
 
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061)\n\tat
 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)\n\tat
 
org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:215)\n\tat
 
org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:110)\n\tat
 
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)\n\tat
 org.eclipse.jetty.server.Server.handle(Server.java:497)\n\tat 
org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:310)\n\tat 
org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:257)\n\tat
 
org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540)\n\tat
 
org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)\n\tat
 
org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)\n\tat
 java.lang.Thread.run(Thread.java:745)\n",
"code": 500

2. I also ran the Index upgrader then the core is Not registering correctly 
with 
"msg": "java.lang.String cannot be cast to java.util.Date"

Is there any solutions with config changes without reindexing entire documents? 

Re: Solr upgrade from 4.x to 7.1

[Erick Erickson]

What advantage do you see in TLOG and/or PULL replicas? The TLOG and
PULL replica types are for some pretty specific use cases,
particularly high-indexing-throughput cases where you can't afford to
index each doc on every node in your cluster. If you can afford the
CPU cycles to index on every node, I'd stick with NRT replicas.

Yes, though, you can mix/match the types. I question whether you
_want_ to, but you know your app best.

Best,
Erick

On Fri, Dec 15, 2017 at 8:44 AM, Drooy Drooy  wrote:
> Hi Erick/Robi,
>
> Thanks for your replies! one more question, if I go with solrcloud and
> having PULL/TLOG replication mixed in the cluster, by the documentation,
> this would have Master/Slave mode benefit as well,  does that seem feasible
> to you? are there any projects adopting this new feature in 7.0/7.1 ?
>
> Thanks
> Drooy
>
>
> On Thu, Dec 14, 2017 at 7:15 PM, Erick Erickson 
> wrote:
>
>> Completely agree with Robert. I'd also add that you should _not_ copy
>> your configs from 4x. Start with the 7x configs and add any
>> customizations but don't change things like luceneMatchVersion and the
>> like.
>>
>> If you simply _cannot_ reindex, take a look at
>> https://github.com/cominvent/solr-tools/blob/master/
>> upgradeindex/upgradeindex.sh
>>
>> On Thu, Dec 14, 2017 at 2:24 PM, Petersen, Robert (Contr)
>>  wrote:
>> > From what I have read, you can only upgrade to the next major version
>> number without using a tool to convert the indexes to the newer version.
>> But that is still perilous due to deprications etc
>> >
>> >
>> > So I think best advice out there is to spin up a new farm on 7.1
>> (especially from 4.x), make a new collection there, reindex everything into
>> it and then switch over to the new farm. I would also ask the question are
>> you thinking to go to master/slave on 7.1? Wouldn't you want to go with
>> solr cloud?
>> >
>> >
>> > I started with master/slave and yes it is simpler but there is that one
>> single point of failure (the master) for indexing, which is of course
>> easily manually overcome by purposing a slave as the new master and
>> repointing the remaining slaves at the new master however this is a
>> completely manual process you try to avoid in cloud mode.
>> >
>> >
>> > I think you'd need to think this through more fully with the new
>> possibilities available and how you'd want to migrate given your existing
>> environment is so far behind.
>> >
>> >
>> > Thanks
>> >
>> > Robi
>> >
>> > 
>> > From: Drooy Drooy 
>> > Sent: Thursday, December 14, 2017 1:27:53 PM
>> > To: solr-user@lucene.apache.org
>> > Subject: Solr upgrade from 4.x to 7.1
>> >
>> > Hi All,
>> >
>> > We have an in-house project running in Solr 4.7 with Master/Slave mode
>> for
>> > a few years, what is it going to take to upgrade it to SolrCloud with
>> > TLOG/PULL replica mode ?
>> >
>> > I read the upgrade guides, none of them talking about the jump from 4.x
>> to
>> > 7.
>> >
>> > Thanks much
>> >
>> > 
>> >
>> > This communication is confidential. Frontier only sends and receives
>> email on the basis of the terms set out at http://www.frontier.com/email_
>> disclaimer.
>>

Re: Solr upgrade from 4.x to 7.1

[Drooy Drooy]

Hi Erick/Robi,

Thanks for your replies! one more question, if I go with solrcloud and
having PULL/TLOG replication mixed in the cluster, by the documentation,
this would have Master/Slave mode benefit as well,  does that seem feasible
to you? are there any projects adopting this new feature in 7.0/7.1 ?

Thanks
Drooy


On Thu, Dec 14, 2017 at 7:15 PM, Erick Erickson 
wrote:

> Completely agree with Robert. I'd also add that you should _not_ copy
> your configs from 4x. Start with the 7x configs and add any
> customizations but don't change things like luceneMatchVersion and the
> like.
>
> If you simply _cannot_ reindex, take a look at
> https://github.com/cominvent/solr-tools/blob/master/
> upgradeindex/upgradeindex.sh
>
> On Thu, Dec 14, 2017 at 2:24 PM, Petersen, Robert (Contr)
>  wrote:
> > From what I have read, you can only upgrade to the next major version
> number without using a tool to convert the indexes to the newer version.
> But that is still perilous due to deprications etc
> >
> >
> > So I think best advice out there is to spin up a new farm on 7.1
> (especially from 4.x), make a new collection there, reindex everything into
> it and then switch over to the new farm. I would also ask the question are
> you thinking to go to master/slave on 7.1? Wouldn't you want to go with
> solr cloud?
> >
> >
> > I started with master/slave and yes it is simpler but there is that one
> single point of failure (the master) for indexing, which is of course
> easily manually overcome by purposing a slave as the new master and
> repointing the remaining slaves at the new master however this is a
> completely manual process you try to avoid in cloud mode.
> >
> >
> > I think you'd need to think this through more fully with the new
> possibilities available and how you'd want to migrate given your existing
> environment is so far behind.
> >
> >
> > Thanks
> >
> > Robi
> >
> > 
> > From: Drooy Drooy 
> > Sent: Thursday, December 14, 2017 1:27:53 PM
> > To: solr-user@lucene.apache.org
> > Subject: Solr upgrade from 4.x to 7.1
> >
> > Hi All,
> >
> > We have an in-house project running in Solr 4.7 with Master/Slave mode
> for
> > a few years, what is it going to take to upgrade it to SolrCloud with
> > TLOG/PULL replica mode ?
> >
> > I read the upgrade guides, none of them talking about the jump from 4.x
> to
> > 7.
> >
> > Thanks much
> >
> > 
> >
> > This communication is confidential. Frontier only sends and receives
> email on the basis of the terms set out at http://www.frontier.com/email_
> disclaimer.
>

Re: Solr upgrade from 4.x to 7.1

[Shawn Heisey]

On 12/14/2017 2:27 PM, Drooy Drooy wrote:
> We have an in-house project running in Solr 4.7 with Master/Slave mode for
> a few years, what is it going to take to upgrade it to SolrCloud with
> TLOG/PULL replica mode ?
>
> I read the upgrade guides, none of them talking about the jump from 4.x to
> 7.

I would strongly recommend that you treat the new version as an entirely
new deployment, not as something you're going to upgrade.  Build new
collections with configs designed from 7.x examples and reindex
completely from scratch.

Many configs that people are using with version 4 were actually designed
for earlier versions and contain things that won't even work with 5.x,
let alone 7.x.  Even if you have a config built specifically for 4.x, it
is still likely that it's not going to work at all in 7.x without at
least some minimal updates.

The number of changes you're probably going to WANT (in addition to
those that you NEED) will probably make your config incompatible with
your existing index data.  It is extremely likely that you will need to
reindex at some point.  Three major versions is an *enormous* change to
how Solr works.

Just in case you might need it, here's a wiki page about reindexing. 
You may already be aware of what that means:

https://wiki.apache.org/solr/HowToReindex

Thanks,
Shawn

Re: Solr upgrade from 4.x to 7.1

[Erick Erickson]

Completely agree with Robert. I'd also add that you should _not_ copy
your configs from 4x. Start with the 7x configs and add any
customizations but don't change things like luceneMatchVersion and the
like.

If you simply _cannot_ reindex, take a look at
https://github.com/cominvent/solr-tools/blob/master/upgradeindex/upgradeindex.sh

On Thu, Dec 14, 2017 at 2:24 PM, Petersen, Robert (Contr)
 wrote:
> From what I have read, you can only upgrade to the next major version number 
> without using a tool to convert the indexes to the newer version. But that is 
> still perilous due to deprications etc
>
>
> So I think best advice out there is to spin up a new farm on 7.1 (especially 
> from 4.x), make a new collection there, reindex everything into it and then 
> switch over to the new farm. I would also ask the question are you thinking 
> to go to master/slave on 7.1? Wouldn't you want to go with solr cloud?
>
>
> I started with master/slave and yes it is simpler but there is that one 
> single point of failure (the master) for indexing, which is of course easily 
> manually overcome by purposing a slave as the new master and repointing the 
> remaining slaves at the new master however this is a completely manual 
> process you try to avoid in cloud mode.
>
>
> I think you'd need to think this through more fully with the new 
> possibilities available and how you'd want to migrate given your existing 
> environment is so far behind.
>
>
> Thanks
>
> Robi
>
> 
> From: Drooy Drooy 
> Sent: Thursday, December 14, 2017 1:27:53 PM
> To: solr-user@lucene.apache.org
> Subject: Solr upgrade from 4.x to 7.1
>
> Hi All,
>
> We have an in-house project running in Solr 4.7 with Master/Slave mode for
> a few years, what is it going to take to upgrade it to SolrCloud with
> TLOG/PULL replica mode ?
>
> I read the upgrade guides, none of them talking about the jump from 4.x to
> 7.
>
> Thanks much
>
> 
>
> This communication is confidential. Frontier only sends and receives email on 
> the basis of the terms set out at http://www.frontier.com/email_disclaimer.

Re: Solr upgrade from 4.x to 7.1

[Petersen, Robert (Contr)]

>From what I have read, you can only upgrade to the next major version number 
>without using a tool to convert the indexes to the newer version. But that is 
>still perilous due to deprications etc


So I think best advice out there is to spin up a new farm on 7.1 (especially 
from 4.x), make a new collection there, reindex everything into it and then 
switch over to the new farm. I would also ask the question are you thinking to 
go to master/slave on 7.1? Wouldn't you want to go with solr cloud?


I started with master/slave and yes it is simpler but there is that one single 
point of failure (the master) for indexing, which is of course easily manually 
overcome by purposing a slave as the new master and repointing the remaining 
slaves at the new master however this is a completely manual process you try to 
avoid in cloud mode.


I think you'd need to think this through more fully with the new possibilities 
available and how you'd want to migrate given your existing environment is so 
far behind.


Thanks

Robi


From: Drooy Drooy 
Sent: Thursday, December 14, 2017 1:27:53 PM
To: solr-user@lucene.apache.org
Subject: Solr upgrade from 4.x to 7.1

Hi All,

We have an in-house project running in Solr 4.7 with Master/Slave mode for
a few years, what is it going to take to upgrade it to SolrCloud with
TLOG/PULL replica mode ?

I read the upgrade guides, none of them talking about the jump from 4.x to
7.

Thanks much



This communication is confidential. Frontier only sends and receives email on 
the basis of the terms set out at http://www.frontier.com/email_disclaimer.

Solr upgrade from 4.x to 7.1

[Drooy Drooy]

Hi All,

We have an in-house project running in Solr 4.7 with Master/Slave mode for
a few years, what is it going to take to upgrade it to SolrCloud with
TLOG/PULL replica mode ?

I read the upgrade guides, none of them talking about the jump from 4.x to
7.

Thanks much

Re: SOLR Upgrade 3.x to 4.10

[abhi Abhishek]

Thanks Erick and Shawn for the input. it makes more sense to move to SOLR
5.x but we would like to get there in few iterations gradually making
incremental changes to have a smooth cut over.

our index size is 3TB (10 shards of 300G each), i was looking for a
alternate route which would save me from pain of re-indexing. any thoughts
for the same would help.

Best Regards,
Abhishek


On Wed, Apr 13, 2016 at 6:18 AM, Shawn Heisey  wrote:

> On 4/12/2016 6:10 AM, abhi Abhishek wrote:
> > I have SOLR 3.6 running currently, i am planning to upgrade this to
> > SOLR 4.10. Below were the thoughts we could come up with.
> >
> > 1. in place upgrade
> >I would be making the SOLR 4.10 slave of 3.6 and copy the indexes,
> > and optimize this index.
> >
> >   will optimizing the Lucene 3.3 index on SOLR 4 instance(with Lucene
> > 4.10) change the index structure to Lucene 4.10? if not what would be the
> > version?
>
> Yes, the optimize will change the index structure, but the contents of
> the index will not change, even if changes in Solr's analysis components
> would have resulted in different info going into the index based on your
> schema.  Because the *query* analysis may also change with the upgrade,
> this might cause queries to no longer work the same, unless you reindex
> and verify that your analysis still does what you require.  A few
> changes to analysis components in later versions can be changed back to
> earlier behavior with luceneMatchVersion, but this typically only
> happens with big changes -- such as the major bugfix for
> WordDelimiterFilterFactory in version 4.8.
>
> Reindexing for all upgrades is recommended when possible.
>
> >   if i enable docvalues on certain fields before issuing optimize,
> will
> > it be able to incorporate ( create .dvd & .dvm files ) that in the newly
> > created index?
>
> No.  You must entirely reindex to add docValues.  Optimize just rewrites
> what's already present in the Lucene index.
>
> > 2. Re-Index the data
> >
> > Seeking advice for minimum time to upgrade this with most features of
> SOLR
> > 4.10
>
> This is impossible to answer.  It will depend on how long it takes to
> index your data.  That is very difficult to predict even if a lot of
> information is available.
>
> Thanks,
> Shawn
>
>

Re: SOLR Upgrade 3.x to 4.10

[Shawn Heisey]

On 4/12/2016 6:10 AM, abhi Abhishek wrote:
> I have SOLR 3.6 running currently, i am planning to upgrade this to
> SOLR 4.10. Below were the thoughts we could come up with.
>
> 1. in place upgrade
>I would be making the SOLR 4.10 slave of 3.6 and copy the indexes,
> and optimize this index.
>
>   will optimizing the Lucene 3.3 index on SOLR 4 instance(with Lucene
> 4.10) change the index structure to Lucene 4.10? if not what would be the
> version?

Yes, the optimize will change the index structure, but the contents of
the index will not change, even if changes in Solr's analysis components
would have resulted in different info going into the index based on your
schema.  Because the *query* analysis may also change with the upgrade,
this might cause queries to no longer work the same, unless you reindex
and verify that your analysis still does what you require.  A few
changes to analysis components in later versions can be changed back to
earlier behavior with luceneMatchVersion, but this typically only
happens with big changes -- such as the major bugfix for
WordDelimiterFilterFactory in version 4.8.

Reindexing for all upgrades is recommended when possible.

>   if i enable docvalues on certain fields before issuing optimize, will
> it be able to incorporate ( create .dvd & .dvm files ) that in the newly
> created index?

No.  You must entirely reindex to add docValues.  Optimize just rewrites
what's already present in the Lucene index.

> 2. Re-Index the data
>
> Seeking advice for minimum time to upgrade this with most features of SOLR
> 4.10

This is impossible to answer.  It will depend on how long it takes to
index your data.  That is very difficult to predict even if a lot of
information is available.

Thanks,
Shawn

Re: SOLR Upgrade 3.x to 4.10

[Erick Erickson]

I would always re-index if possible, it's more certain than upgrading
the indexes. It's "not possible" when it takes very long

And why go for 4.10 rather than 5.5 (Note, 5.5.1 will be out Real Soon
Now). If you can re-index, I'd really think about upgrading to 5.5.1
and going from there.

Best,
Erick

On Tue, Apr 12, 2016 at 5:10 AM, abhi Abhishek  wrote:
> Hi All,
> I have SOLR 3.6 running currently, i am planning to upgrade this to
> SOLR 4.10. Below were the thoughts we could come up with.
>
> 1. in place upgrade
>I would be making the SOLR 4.10 slave of 3.6 and copy the indexes,
> and optimize this index.
>
>   will optimizing the Lucene 3.3 index on SOLR 4 instance(with Lucene
> 4.10) change the index structure to Lucene 4.10? if not what would be the
> version?
>   if i enable docvalues on certain fields before issuing optimize, will
> it be able to incorporate ( create .dvd & .dvm files ) that in the newly
> created index?
>
>
> 2. Re-Index the data
>
> Seeking advice for minimum time to upgrade this with most features of SOLR
> 4.10
>
> Thanks in Advance
>
> Best Regards,
> Abhishek

SOLR Upgrade 3.x to 4.10

[abhi Abhishek]

Hi All,
I have SOLR 3.6 running currently, i am planning to upgrade this to
SOLR 4.10. Below were the thoughts we could come up with.

1. in place upgrade
   I would be making the SOLR 4.10 slave of 3.6 and copy the indexes,
and optimize this index.

  will optimizing the Lucene 3.3 index on SOLR 4 instance(with Lucene
4.10) change the index structure to Lucene 4.10? if not what would be the
version?
  if i enable docvalues on certain fields before issuing optimize, will
it be able to incorporate ( create .dvd & .dvm files ) that in the newly
created index?


2. Re-Index the data

Seeking advice for minimum time to upgrade this with most features of SOLR
4.10

Thanks in Advance

Best Regards,
Abhishek

solr upgrade to 5.5 from 4.4

[Anuj Lal]

I have made changes as listed in document ( sol.xml, core.properties, schema 
changes) before i did upgrade
I am using solrcloud deployment
Doing node by node upgrade.
Almost everything work fine. Except if new upgraded  node ( node which is 
upgraded to 5.5) become leader than even if that node goes down other node ( 
node which is still in 4.4) is not coming as leader. In admin ui, down node 
continues as leader node

Also if upgraded node is 5.5 and leader, index can still be replicated to other 
other active 4.4 node? Will system work if 5.5 leader goes down? 
Has anyone done 4.x to 5.x rolling upgrade?

AL

Re: Solr upgrade to latest version

[Erick Erickson]

Did you look at the rest of this thread? There are some comments there.

The CHANGES.txt file will guide you through each intermediate step.

There's nothing going straight from 1.4 to 4.x. You could go from 1.4 -> 3.x
then 3.x->4.x, but frankly I'd just start with a stock 4.x distro and
transfer over
only the things you've changed (like schema definitions, NOT the whole file,
see above) and re-index.

Best,
Erick

On Tue, Sep 23, 2014 at 10:23 PM, Vivek Misra  wrote:

> Hi,
>
> Currently I am using SOLR 1.4.1 and want to migrate to SOLR 4.9.
>
> Is there any manual or link for 1.4 to 4.9? Which can guide step by step on
>
> 1. solrconfig.xml changes
>
> 2. schema.xml changes
>
> 3. changes required in version 1.4.1 queries.
>
>
> Thanks
>
> Vivek
>
>
>
>
>
>
> On Tue, Sep 23, 2014 at 9:19 AM, Danesh Kuruppu 
> wrote:
>
> > Thanks Alex and Erick for quick response,
> > This is really helpful.
> >
> > On Tue, Sep 23, 2014 at 1:19 AM, Erick Erickson  >
> > wrote:
> >
> > > Probably go for 4.9.1. There'll be a 4.10.1 out in the not-too-distant
> > > future that you can upgrade to if you wish. 4.9.1 -> 4.10.1 should be
> > > quite painless.
> > >
> > > But do _not_ copy your schema.xml and solrconfig.xml files over form
> > > 1.4 to 4.x. There are some fairly easy ways to shoot yourself in the
> > > foot there. Take the stock distribution configuration files and copy
> > > _parts_ of your schema.xml and solrconfig.xml you care about.
> > >
> > > If you're using multiple cores, read about core discovery here:
> > > https://wiki.apache.org/solr/Core%20Discovery%20(4.4%20and%20beyond)
> > >
> > > And be very aware that you should _not_ remove any of the _field_
> > > entries in schema.xml. In particular _version_ and _root_ should be
> > > left alone. As well as the "id" field.
> > >
> > > And you'll have to re-index everything; Solr 4.x will not read Solr
> > > 1.4 indexes. If that's impossible, you'll have to upgrade from 1.4 to
> > > 3.x, optimize your index, then upgrade from 3.x to 4.x, add some
> > > documents, and optimize/force_merge again.
> > >
> > > HTH
> > > Erick
> > >
> > > On Mon, Sep 22, 2014 at 2:29 AM, Danesh Kuruppu 
> > > wrote:
> > > > Hi all,
> > > >
> > > > I currently working on upgrade sorl 1.4.1 to sorl latest stable
> > release.
> > > >
> > > > What is the latest stable release I can use?
> > > > Is there specfic things I need to look at when upgrade.
> > > >
> > > > Need help
> > > > Thanks
> > > >
> > > > Danesh
> > >
> >
>

Re: Solr upgrade to latest version

[Vivek Misra]

Hi,

Currently I am using SOLR 1.4.1 and want to migrate to SOLR 4.9.

Is there any manual or link for 1.4 to 4.9? Which can guide step by step on

1. solrconfig.xml changes

2. schema.xml changes

3. changes required in version 1.4.1 queries.


Thanks

Vivek






On Tue, Sep 23, 2014 at 9:19 AM, Danesh Kuruppu 
wrote:

> Thanks Alex and Erick for quick response,
> This is really helpful.
>
> On Tue, Sep 23, 2014 at 1:19 AM, Erick Erickson 
> wrote:
>
> > Probably go for 4.9.1. There'll be a 4.10.1 out in the not-too-distant
> > future that you can upgrade to if you wish. 4.9.1 -> 4.10.1 should be
> > quite painless.
> >
> > But do _not_ copy your schema.xml and solrconfig.xml files over form
> > 1.4 to 4.x. There are some fairly easy ways to shoot yourself in the
> > foot there. Take the stock distribution configuration files and copy
> > _parts_ of your schema.xml and solrconfig.xml you care about.
> >
> > If you're using multiple cores, read about core discovery here:
> > https://wiki.apache.org/solr/Core%20Discovery%20(4.4%20and%20beyond)
> >
> > And be very aware that you should _not_ remove any of the _field_
> > entries in schema.xml. In particular _version_ and _root_ should be
> > left alone. As well as the "id" field.
> >
> > And you'll have to re-index everything; Solr 4.x will not read Solr
> > 1.4 indexes. If that's impossible, you'll have to upgrade from 1.4 to
> > 3.x, optimize your index, then upgrade from 3.x to 4.x, add some
> > documents, and optimize/force_merge again.
> >
> > HTH
> > Erick
> >
> > On Mon, Sep 22, 2014 at 2:29 AM, Danesh Kuruppu 
> > wrote:
> > > Hi all,
> > >
> > > I currently working on upgrade sorl 1.4.1 to sorl latest stable
> release.
> > >
> > > What is the latest stable release I can use?
> > > Is there specfic things I need to look at when upgrade.
> > >
> > > Need help
> > > Thanks
> > >
> > > Danesh
> >
>

Re: Solr upgrade to latest version

[Danesh Kuruppu]

Thanks Alex and Erick for quick response,
This is really helpful.

On Tue, Sep 23, 2014 at 1:19 AM, Erick Erickson 
wrote:

> Probably go for 4.9.1. There'll be a 4.10.1 out in the not-too-distant
> future that you can upgrade to if you wish. 4.9.1 -> 4.10.1 should be
> quite painless.
>
> But do _not_ copy your schema.xml and solrconfig.xml files over form
> 1.4 to 4.x. There are some fairly easy ways to shoot yourself in the
> foot there. Take the stock distribution configuration files and copy
> _parts_ of your schema.xml and solrconfig.xml you care about.
>
> If you're using multiple cores, read about core discovery here:
> https://wiki.apache.org/solr/Core%20Discovery%20(4.4%20and%20beyond)
>
> And be very aware that you should _not_ remove any of the _field_
> entries in schema.xml. In particular _version_ and _root_ should be
> left alone. As well as the "id" field.
>
> And you'll have to re-index everything; Solr 4.x will not read Solr
> 1.4 indexes. If that's impossible, you'll have to upgrade from 1.4 to
> 3.x, optimize your index, then upgrade from 3.x to 4.x, add some
> documents, and optimize/force_merge again.
>
> HTH
> Erick
>
> On Mon, Sep 22, 2014 at 2:29 AM, Danesh Kuruppu 
> wrote:
> > Hi all,
> >
> > I currently working on upgrade sorl 1.4.1 to sorl latest stable release.
> >
> > What is the latest stable release I can use?
> > Is there specfic things I need to look at when upgrade.
> >
> > Need help
> > Thanks
> >
> > Danesh
>

Re: Solr upgrade to latest version

[Erick Erickson]

Probably go for 4.9.1. There'll be a 4.10.1 out in the not-too-distant
future that you can upgrade to if you wish. 4.9.1 -> 4.10.1 should be
quite painless.

But do _not_ copy your schema.xml and solrconfig.xml files over form
1.4 to 4.x. There are some fairly easy ways to shoot yourself in the
foot there. Take the stock distribution configuration files and copy
_parts_ of your schema.xml and solrconfig.xml you care about.

If you're using multiple cores, read about core discovery here:
https://wiki.apache.org/solr/Core%20Discovery%20(4.4%20and%20beyond)

And be very aware that you should _not_ remove any of the _field_
entries in schema.xml. In particular _version_ and _root_ should be
left alone. As well as the "id" field.

And you'll have to re-index everything; Solr 4.x will not read Solr
1.4 indexes. If that's impossible, you'll have to upgrade from 1.4 to
3.x, optimize your index, then upgrade from 3.x to 4.x, add some
documents, and optimize/force_merge again.

HTH
Erick

On Mon, Sep 22, 2014 at 2:29 AM, Danesh Kuruppu  wrote:
> Hi all,
>
> I currently working on upgrade sorl 1.4.1 to sorl latest stable release.
>
> What is the latest stable release I can use?
> Is there specfic things I need to look at when upgrade.
>
> Need help
> Thanks
>
> Danesh

Re: Solr upgrade to latest version

[Alexandre Rafalovitch]

4.10.1 out shortly is a good bet.

No idea about the upgrade specifically, but I would probably do some
reading of recent solrconfig.xml to get a hint of new features. Also,
schema.xml has a version number at the top. The default changed which
is controlled by that version number. So, it is something to keep in
mind.

Regards,
   Alex.
Personal: http://www.outerthoughts.com/ and @arafalov
Solr resources and newsletter: http://www.solr-start.com/ and @solrstart
Solr popularizers community: https://www.linkedin.com/groups?gid=6713853


On 22 September 2014 05:29, Danesh Kuruppu  wrote:
> Hi all,
>
> I currently working on upgrade sorl 1.4.1 to sorl latest stable release.
>
> What is the latest stable release I can use?
> Is there specfic things I need to look at when upgrade.
>
> Need help
> Thanks
>
> Danesh

Solr upgrade to latest version

[Danesh Kuruppu]

Hi all,

I currently working on upgrade sorl 1.4.1 to sorl latest stable release.

What is the latest stable release I can use?
Is there specfic things I need to look at when upgrade.

Need help
Thanks

Danesh

NumberFormatException in solr.SpatialRecursivePrefixTreeFieldType in solr upgrade

[Kamal Kishore Aggarwal]

I am using following field type with solr 4.2 & its working fine.




But, when I am upgrading solr to solr 4.7.1, it is reporting following
errors while posting docs:
Caused by: com.spatial4j.core.exception.InvalidShapeException:
java.lang.NumberFormatException: For input string: "78.42968,30.7,78.45"
at
org.apache.solr.util.SpatialUtils.parsePoint(SpatialUtils.java:68)
at
org.apache.solr.util.SpatialUtils.parsePointSolrException(SpatialUtils.java:84)
... 45 more
Caused by: java.lang.NumberFormatException: For input string:
"78.42968,30.7,78.45"

I am posting following doc value to solr.
   

With Thanks & Regards
Kamal Kishore

Re: SSLinitializationException after SOLR upgrade

[lakshmi guruparan]

Hi Hoss,

Thanks for your response. As pointed we are running Solr on a JVM that is
configured to use SSL Key store. We are not specifying the password while
running the JVM, we are using keystore for secured access. The issue that
we are facing now is, we are able to make few initiall connections. But we
get the above mentioned exception intermittently and not always. I believe
if the reason is incorrect keystore then this should not succeed even once.
After a restart of the server we are able to see few inital successful
transaction, but it fails in a while.
Could you please let help us on  this.

Thanks,
Lakshmi



On Fri, Jan 3, 2014 at 12:55 PM, Chris Hostetter
wrote:

>
> : We recently ungraded from solr 3.5 to solr4.4 . After the upgrade we are
> : facing the following issue. Could anyone please suggest on what could be
> : done.
>
> You are aparently running Solr code from a JVM configured to use an SSL
> keystore which has a password configured on it, and you either have not
> specified hte password when running the JVM, or you are attempting ot use
> the wrong keystore password...
>
> :  Caused by: java.io.IOException: Keystore was tampered with, or password
> : was incorrect
> ...
> : Caused by: java.security.UnrecoverableKeyException: Password verification
> : failed
>
> You are seeing this after upgrading because Solr (as of 4.2) now uses
> HttpClient in a way that respects system default HTTP settings (and you
> evidently have a setting fo the keystore but your corrisponding setting
> for the keystore password is wrong/missing)...
>
>
> https://hc.apache.org/httpcomponents-client-ga/httpclient/apidocs/org/apache/http/impl/client/SystemDefaultHttpClient.html
>
>
>
>
> -Hoss
> http://www.lucidworks.com/
>

Re: SSLinitializationException after SOLR upgrade

[Chris Hostetter]

: We recently ungraded from solr 3.5 to solr4.4 . After the upgrade we are
: facing the following issue. Could anyone please suggest on what could be
: done.

You are aparently running Solr code from a JVM configured to use an SSL 
keystore which has a password configured on it, and you either have not 
specified hte password when running the JVM, or you are attempting ot use 
the wrong keystore password...

:  Caused by: java.io.IOException: Keystore was tampered with, or password
: was incorrect
...
: Caused by: java.security.UnrecoverableKeyException: Password verification
: failed

You are seeing this after upgrading because Solr (as of 4.2) now uses 
HttpClient in a way that respects system default HTTP settings (and you 
evidently have a setting fo the keystore but your corrisponding setting 
for the keystore password is wrong/missing)...

https://hc.apache.org/httpcomponents-client-ga/httpclient/apidocs/org/apache/http/impl/client/SystemDefaultHttpClient.html




-Hoss
http://www.lucidworks.com/

SSLinitializationException after SOLR upgrade

[lakshmi guruparan]

Hi All,

We recently ungraded from solr 3.5 to solr4.4 . After the upgrade we are
facing the following issue. Could anyone please suggest on what could be
done.

INFO [2013-12-13 07:54:50,149] [threadPoolTaskExecutor-2] [HttpClientUtil]
[HttpClientUtil.java:103] - Creating new http client,
config:maxConnections=128&maxConnectionsPerHost=32&followRedirects=false
org.apache.http.conn.ssl.SSLInitializationException: Failure initializing
default system SSL context
at
org.apache.http.conn.ssl.SSLSocketFactory.createSystemSSLContext(SSLSocketFactory.java:368)
at
org.apache.http.conn.ssl.SSLSocketFactory.getSystemSocketFactory(SSLSocketFactory.java:204)
at
org.apache.http.impl.conn.SchemeRegistryFactory.createSystemDefault(SchemeRegistryFactory.java:82)
at
org.apache.http.impl.client.SystemDefaultHttpClient.createClientConnectionManager(SystemDefaultHttpClient.java:118)
at
org.apache.http.impl.client.AbstractHttpClient.getConnectionManager(AbstractHttpClient.java:466)
at
org.apache.solr.client.solrj.impl.HttpClientUtil.setMaxConnections(HttpClientUtil.java:179)
at
org.apache.solr.client.solrj.impl.HttpClientConfigurer.configure(HttpClientConfigurer.java:33)
at
org.apache.solr.client.solrj.impl.HttpClientUtil.configureClient(HttpClientUtil.java:115)
at
org.apache.solr.client.solrj.impl.HttpClientUtil.createClient(HttpClientUtil.java:105)
at
org.apache.solr.client.solrj.impl.HttpSolrServer.(HttpSolrServer.java:154)
at
org.apache.solr.client.solrj.impl.HttpSolrServer.(HttpSolrServer.java:127)
at
com.cisco.npa.solr.SolrService.getSolrService(SolrService.java:47)
at
com.cisco.npa.excel.ExcelTask.generateExcelDoc(ExcelTask.java:109)
at com.cisco.npa.excel.ExcelTask.run(ExcelTask.java:75)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)

 Caused by: java.io.IOException: Keystore was tampered with, or password
was incorrect
at
sun.security.provider.JavaKeyStore.engineLoad(JavaKeyStore.java:771)
at
sun.security.provider.JavaKeyStore$JKS.engineLoad(JavaKeyStore.java:38)
at java.security.KeyStore.load(KeyStore.java:1185)
at
org.apache.http.conn.ssl.SSLSocketFactory.createSystemSSLContext(SSLSocketFactory.java:281)
at
org.apache.http.conn.ssl.SSLSocketFactory.createSystemSSLContext(SSLSocketFactory.java:366)
... 16 more
Caused by: java.security.UnrecoverableKeyException: Password verification
failed
at
sun.security.provider.JavaKeyStore.engineLoad(JavaKeyStore.java:769)
... 20 more

Thanks,
Lakshmi

RE: Solr upgrade from 1.4 to 3.6

[Manepalli, Kalyan]

Chantal,
Thanks for the reply. I will try it out. 

Thanks,
Kalyan Manepalli


-Original Message-
From: Chantal Ackermann [mailto:c.ackerm...@it-agenten.com] 
Sent: Wednesday, August 01, 2012 3:55 AM
To: solr-user@lucene.apache.org
Subject: Re: Solr upgrade from 1.4 to 3.6

Hi Kalyan,

that is becouse SolrJ uses "javabin" as format which has class version numbers 
in the serialized objects that do not match. Set the format to XML ("wt" 
parameter) and it will work (maybe JSON would, as well).

Chantal
 

Am 31.07.2012 um 20:50 schrieb Manepalli, Kalyan:

> Hi all,
>We are trying to upgrade our solr instance from 1.4 to 3.6. We 
> use SolrJ API to fetch the data from index. We see that SolrJ 3.6 version is 
> not compatible with index generated with 1.4.
> Is this known issue and is there a workaround for this.
> 
> Thanks,
> Kalyan Manepalli
> 

Re: Solr upgrade from 1.4 to 3.6

[Chantal Ackermann]

Hi Kalyan,

that is becouse SolrJ uses "javabin" as format which has class version numbers 
in the serialized objects that do not match. Set the format to XML ("wt" 
parameter) and it will work (maybe JSON would, as well).

Chantal
 

Am 31.07.2012 um 20:50 schrieb Manepalli, Kalyan:

> Hi all,
>We are trying to upgrade our solr instance from 1.4 to 3.6. We 
> use SolrJ API to fetch the data from index. We see that SolrJ 3.6 version is 
> not compatible with index generated with 1.4.
> Is this known issue and is there a workaround for this.
> 
> Thanks,
> Kalyan Manepalli
> 

Solr upgrade from 1.4 to 3.6

[Manepalli, Kalyan]

Hi all,
We are trying to upgrade our solr instance from 1.4 to 3.6. We 
use SolrJ API to fetch the data from index. We see that SolrJ 3.6 version is 
not compatible with index generated with 1.4.
Is this known issue and is there a workaround for this.

Thanks,
Kalyan Manepalli

Re: Solr Upgrade from 1.4 to 3.1

[Markus Jelsma]

Everything you need to know about upgrading is listed in CHANGES.txt

On Wednesday 31 August 2011 18:14:11 Pawan Darira wrote:
> Hi
> 
> I want to upgrade my solr version 1.4 to 3.1. Please suggest the steps &
> what challenges might occur.
> 
> I have started using solr from 1.4 & this is my 1st experience to upgrade
> the version
> 
> thanks
> Pawan

-- 
Markus Jelsma - CTO - Openindex
http://www.linkedin.com/in/markus17
050-8536620 / 06-50258350

Solr Upgrade from 1.4 to 3.1

[Pawan Darira]

Hi

I want to upgrade my solr version 1.4 to 3.1. Please suggest the steps &
what challenges might occur.

I have started using solr from 1.4 & this is my 1st experience to upgrade
the version

thanks
Pawan

Re: SOlr upgrade: Invalid version (expected 2, but 1) error when using shards

[Shawn Heisey]

On 8/16/2011 4:16 AM, olivier sallou wrote:

I just migrated to solr 3.3 from 1.4.1.
My index is still in 1.4.1 format (will be migrated soon).

I have an error when I use sharding with the new version:

org.apache.solr.common.SolrException: java.lang.RuntimeException: Invalid
version (expected 2, but 1) or the data in not in 'javabin' format

However, if I request each shard independently (/request), answer is
correct. So the error is triggered only with the shard mechanism.


In version 3.1, the javabin format was changed, it's completely 
incompatible with 1.4.1 and earlier at the application level, which 
should have nothing to do with the index format.  Javabin is used in 
distributed search and by SolrJ.


It sounds like you either have an old SolrJ version talking to the new 
Solr version, or you are requesting data from your shards using an old 
version of Solr.  If it's the latter, just upgrade the Solr instance 
that serves as the broker/middleman between your application and your 
shards.


If it's SolrJ, you have two choices.  You can either upgrade your SolrJ 
jar and the jars found in solrj-lib, or keep using the old version and 
add the following line to your code right after your server object is 
created.  This tells SolrJ to use the XML format, which works on any 
version:


server.setParser(new XMLResponseParser());

You'll also need to import 
org.apache.solr.client.solrj.impl.XMLResponseParser for the above line 
to work.


Thanks,
Shawn

SOlr upgrade: Invalid version (expected 2, but 1) error when using shards

[olivier sallou]

Hi,
I just migrated to solr 3.3 from 1.4.1.
My index is still in 1.4.1 format (will be migrated soon).

I have an error when I use sharding with the new version:

org.apache.solr.common.SolrException: java.lang.RuntimeException: Invalid
version (expected 2, but 1) or the data in not in 'javabin' format

However, if I request each shard independently (/request), answer is
correct. So the error is triggered only with the shard mechanism.

While I foresee to upgrade my indexes, I'd like to understand the issue,
e.g. is it an "upgrade" issue or don't shards support using an "old" format.

Thanks

Olivier

Re: Solr - upgrade from 1.4.1 to 3.1 - finding AbstractSolrTestCase binaries - help please?

[lboutros]

There is a jar for the tests in solr.
I added this dependency in my pom.xml :


org.apache.solr
solr-core
3.1-SNAPSHOT
tests
test
jar


Ludovic.

-
Jouve
France.
--
View this message in context: 
http://lucene.472066.n3.nabble.com/Solr-upgrade-from-1-4-1-to-3-1-finding-AbstractSolrTestCase-binaries-help-please-tp2845011p2846223.html
Sent from the Solr - User mailing list archive at Nabble.com.

Solr - upgrade from 1.4.1 to 3.1 - finding AbstractSolrTestCase binaries - help please?

[Bob Sandiford]

HI, all.

I'm working on upgrading from 1.4.1 to 3.1, and I'm having some troubles with 
some of the unit test code for our custom Filters.  We wrote the tests to 
extend AbstractSolrTestCase, and I've been reading the thread about the 
test-harness elements not being present in the 3.1 distributables. [1]

So, I have checked out the 3.1 branch code and built that (ant 
generate-maven-artifacts), and I've found the 
lucene-test-framework-3.1-xxx.jar(s).  However, these contain only the lucene 
level framework elements, and none of the solr.

Did the solr test framework actually get built and embedded in one of the solr 
jars somewhere?  Or, if not, is there some way to build a jar that contains the 
solr portion of the test harnesses?

[1] SOLR-2061 Generate jar 
containing test classes.
*
Thanks!

Bob Sandiford | Lead Software Engineer | SirsiDynix
P: 800.288.8020 X6943 | bob.sandif...@sirsidynix.com
www.sirsidynix.com

Re: solr upgrade question

[Johannes Goll]

Hi Alexander,

I have posted same question a few month ago. The only solution that came up
was to regenerate the index files using the new  version. How did you do
this exactly with
luke 1.0.1 ? Would you mind sharing some of that magic ?

Best,
Johannes


2011/3/31 Alexander Aristov 

> Didn't get any responses.
>
> But I tried luke 1.0.1 and it did the magic. I run optimization and after
> that solr got up.
>
> Best Regards
> Alexander Aristov
>
>
> On 30 March 2011 15:47, Alexander Aristov  >wrote:
>
> > People
> >
> > Is were way to upgrade existsing index from solr 1.4 to solr 4(trunk).
> When
> > I configured solr 4 and launched it complained about incorrect lucence
> file
> > version (3 instead of old 2)
> >
> > Are there any procedures to convert index?
> >
> >
> > Best Regards
> > Alexander Aristov
> >
>

Re: solr upgrade question

[Alexander Aristov]

Didn't get any responses.

But I tried luke 1.0.1 and it did the magic. I run optimization and after
that solr got up.

Best Regards
Alexander Aristov


On 30 March 2011 15:47, Alexander Aristov wrote:

> People
>
> Is were way to upgrade existsing index from solr 1.4 to solr 4(trunk). When
> I configured solr 4 and launched it complained about incorrect lucence file
> version (3 instead of old 2)
>
> Are there any procedures to convert index?
>
>
> Best Regards
> Alexander Aristov
>

solr upgrade question

[Alexander Aristov]

People

Is were way to upgrade existsing index from solr 1.4 to solr 4(trunk). When
I configured solr 4 and launched it complained about incorrect lucence file
version (3 instead of old 2)

Are there any procedures to convert index?


Best Regards
Alexander Aristov