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 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: +44 

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 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 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

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.

Re: Solr Upgrade socketTimeout issue in 8.2

[kshitij tyagi]

Hi Erick,

Thanks for the response.

1. We have started from zero documents and are observing socketTimeout
intermittently while indexing also.

2. We are not using schemaless as we are aware of the drawbacks and have a
well defined schema.

3. We have tried async but it does not help.

4. We tried increasing timeout as mentioned in
https://issues.apache.org/jira/browse/SOLR-13605 by using
withConnectionTimeout() and withSocketTimeout()

5. Our System was pretty stable earlier but as we upgraded to 8.2 from 6.6
version this issue is making Solrcloud system unstable

here is the detailed log which we are observing intermittently at time of
indexing:

ERROR (OverseerThreadFactory-9-thread-3-processing-n:prod-cloud2.net:8983_solr)
[   ] o.a.s.c.a.c.OverseerCollectionMessageHandler Error from shard:
http://prod-cloud2.net:8983/solr =>
org.apache.solr.client.solrj.SolrServerException: Timeout occurred while
waiting response from server at: http://prodcloud2.net:8983/solr
at
org.apache.solr.client.solrj.impl.HttpSolrClient.executeMethod(HttpSolrClient.java:667)
org.apache.solr.client.solrj.SolrServerException: Timeout occurred while
waiting response from server at: http://prod-cloud2.net:8983/solr
at
org.apache.solr.client.solrj.impl.HttpSolrClient.executeMethod(HttpSolrClient.java:667)
~[?:?]
at
org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:262)
~[?:?]
at
org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:245)
~[?:?]
at org.apache.solr.client.solrj.SolrClient.request(SolrClient.java:1274)
~[?:?]
at
org.apache.solr.handler.component.HttpShardHandlerFactory$1.request(HttpShardHandlerFactory.java:176)
~[?:?]
at
org.apache.solr.handler.component.HttpShardHandler.lambda$submit$0(HttpShardHandler.java:199)
~[?:?]
at
org.apache.solr.handler.component.HttpShardHandler.dt_access$927(HttpShardHandler.java)
~[?:?]
at java.util.concurrent.FutureTask.run(Unknown Source) ~[?:1.8.0_131]
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
~[?:1.8.0_131]
at java.util.concurrent.FutureTask.run(Unknown Source) ~[?:1.8.0_131]
at
com.codahale.metrics.InstrumentedExecutorService$InstrumentedRunnable.run(InstrumentedExecutorService.java:181)
~[metrics-core-4.0.5.jar:4.0.5]
at
org.apache.solr.common.util.ExecutorUtil$MDCAwareThreadPoolExecutor.lambda$execute$0(ExecutorUtil.java:209)
~[?:?]
at
org.apache.solr.common.util.ExecutorUtil$MDCAwareThreadPoolExecutor.dt_access$304(ExecutorUtil.java)
~[?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
~[?:1.8.0_131]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
~[?:1.8.0_131]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_131]
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method) ~[?:1.8.0_131]
at java.net.SocketInputStream.socketRead(Unknown Source) ~[?:1.8.0_131]
at java.net.SocketInputStream.read(Unknown Source) ~[?:1.8.0_131]
at java.net.SocketInputStream.read(Unknown Source) ~[?:1.8.0_131]
at
org.apache.http.impl.io.SessionInputBufferImpl.streamRead(SessionInputBufferImpl.java:137)
~[?:?]
at
org.apache.http.impl.io.SessionInputBufferImpl.fillBuffer(SessionInputBufferImpl.java:153)
~[?:?]
at
org.apache.http.impl.io.SessionInputBufferImpl.readLine(SessionInputBufferImpl.java:282)
~[?:?]
at
org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:138)
~[?:?]
at
org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:56)
~[?:?]
at
org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:259)
~[?:?]
at
org.apache.http.impl.DefaultBHttpClientConnection.receiveResponseHeader(DefaultBHttpClientConnection.java:163)
~[?:?]
at
org.apache.http.impl.conn.CPoolProxy.receiveResponseHeader(CPoolProxy.java:165)
~[?:?]
at
org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:273)
~[?:?]
at
org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:125)
~[?:?]
at
org.apache.solr.util.stats.InstrumentedHttpRequestExecutor.execute(InstrumentedHttpRequestExecutor.java:120)
~[?:?]
at
org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:272)
~[?:?]
at
org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:185)
~[?:?]
at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:89)
~[?:?]
at
org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
~[?:?]
at
org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185)
~[?:?]
at
org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83)
~[?:?]
at
org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:56)
~[?:?]
at
org.apache.solr.client.solrj.impl.HttpSolrClient.executeMethod(HttpSolrClient.java:555)
~[?:?]
... 15 more

Thanks for the help, any further suggestions to drill down to problem?

Regards,

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

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

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

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.

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

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 getvive...@gmail.com 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 dknkuru...@gmail.com
 wrote:

  Thanks Alex and Erick for quick response,
  This is really helpful.
 
  On Tue, Sep 23, 2014 at 1:19 AM, Erick Erickson erickerick...@gmail.com
 
  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 dknkuru...@gmail.com
   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 dknkuru...@gmail.com
wrote:

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

 On Tue, Sep 23, 2014 at 1:19 AM, Erick Erickson erickerick...@gmail.com
 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 dknkuru...@gmail.com
  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 dknkuru...@gmail.com 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 erickerick...@gmail.com
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 dknkuru...@gmail.com
 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 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
 

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

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

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 :

dependency
groupIdorg.apache.solr/groupId
artifactIdsolr-core/artifactId
version3.1-SNAPSHOT/version
classifiertests/classifier
scopetest/scope
typejar/type
/dependency

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.

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 alexander.aris...@gmail.comwrote:

 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

[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 alexander.aris...@gmail.com

 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 alexander.aris...@gmail.com
 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