Re: Solr-9.5 | collection creation error

[Jan Høydahl]

Hi,

Do you mind sharing the details with us?

- Exactly how did you install Solr, and what is your ZK_HOST connection string?
- Exactly how did you install ZK, and what is your zoo.cfg, on each of the 
three nodes.
- Which command did you use to create the collection?
- Does this happen every time you try to create a collection, even if you 
create a test collection with _default configset from the UI?
- Did the Solr node crash or recover during this process?
- Are there ERRORs in Zookeeper's log files?

Jan

> 17. apr. 2024 kl. 02:37 skrev HariBabu kuruva :
> 
> HI ,  I am working on a POC, to set up solr-9.5.0. Currently I have
> Solr-8.11.1 installed and running.
> 
> As part of the POC. I have installed Solr-9.5.0(on one node) and Zookeeper
> 3.9.2 (on 3 nodes). This setup is done on the same server where I have
> solr-8.5 running but with different ports.
> 
> Solr and Zookeeper are running on separate nodes and are running fine.
> 
> When I try to create the collection using the below command. I get this
> error. Please help me.
> 
> 
> 
> 2024-04-16 05:17:09.045 ERROR (OverseerThreadFactory-17-thread-5) [c:test1
> s: r: x: t:] o.a.s.c.a.c.CollectionHandlingUtils Collect
> ion test1, operation create failed => org.apache.solr.common.SolrException:
> Underlying core creation failed while creating collecti
> on: test1
>at
> org.apache.solr.cloud.api.collections.CreateCollectionCmd.call(CreateCollectionCmd.java:447)
> org.apache.solr.common.SolrException: Underlying core creation failed while
> creating collection: test1
>at
> org.apache.solr.cloud.api.collections.CreateCollectionCmd.call(CreateCollectionCmd.java:447)
> ~[solr-core-9.5.0.jar:9.5.0
> cdd27dd15c3a6574032e9b1b92b148ab4e383599 - gerlowskija - 2024-02-07
> 15:10:39]
>at
> org.apache.solr.cloud.api.collections.CollApiCmds$TraceAwareCommand.call(CollApiCmds.java:225)
> ~[solr-core-9.5.0.jar:9.5
> .0 cdd27dd15c3a6574032e9b1b92b148ab4e383599 - gerlowskija - 2024-02-07
> 15:10:39]
>at
> org.apache.solr.cloud.api.collections.OverseerCollectionMessageHandler.processMessage(OverseerCollectionMessageHandler.j
> ava:130) ~[solr-core-9.5.0.jar:9.5.0
> cdd27dd15c3a6574032e9b1b92b148ab4e383599 - gerlowskija - 2024-02-07
> 15:10:39]
>at
> org.apache.solr.cloud.OverseerTaskProcessor$Runner.run(OverseerTaskProcessor.java:564)
> ~[solr-core-9.5.0.jar:9.5.0 cdd27
> dd15c3a6574032e9b1b92b148ab4e383599 - gerlowskija - 2024-02-07 15:10:39]
>at
> org.apache.solr.common.util.ExecutorUtil$MDCAwareThreadPoolExecutor.lambda$execute$0(ExecutorUtil.java:299)
> ~[solr-solrj
> -9.5.0.jar:9.5.0 cdd27dd15c3a6574032e9b1b92b148ab4e383599 - gerlowskija -
> 2024-02-07 15:10:39]
>at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> ~[?:?]
>at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> ~[?:?]
>at java.base/java.lang.Thread.run(Thread.java:834) [?:?]
> 2024-04-16 05:17:09.054 ERROR
> (qtp1119242936-23-vmclxeissldi101.corp.equinix.com-50) [c:test1 s: r: x:
> t:vmclxeissldi101.corp.equin
> ix.com-50] o.a.s.h.RequestHandlerBase Client exception =>
> org.apache.solr.common.SolrException: Underlying core creation failed whi
> le creating collection: test1
>at
> org.apache.solr.client.solrj.SolrResponse.getException(SolrResponse.java:56)
> org.apache.solr.common.SolrException: Underlying core creation failed while
> creating collection: test1
>at
> org.apache.solr.client.solrj.SolrResponse.getException(SolrResponse.java:56)
> ~[solr-solrj-9.5.0.jar:9.5.0 cdd27dd15c3a65
> 74032e9b1b92b148ab4e383599 - gerlowskija - 2024-02-07 15:10:39]
>at
> org.apache.solr.handler.admin.api.CreateCollection.createCollection(CreateCollection.java:133)
> ~[solr-core-9.5.0.jar:9.5
> .0 cdd27dd15c3a6574032e9b1b92b148ab4e383599 - gerlowskija - 2024-02-07
> 15:10:39]
>at
> org.apache.solr.handler.admin.CollectionsHandler$CollectionOperation.lambda$static$0(CollectionsHandler.java:517)
> ~[solr
> -core-9.5.0.jar:9.5.0 cdd27dd15c3a6574032e9b1b92b148ab4e383599 -
> gerlowskija - 2024-02-07 15:10:39]
>at
> org.apache.solr.handler.admin.CollectionsHandler$CollectionOperation.execute(CollectionsHandler.java:1264)
> ~[solr-core-9
> .5.0.jar:9.5.0 cdd27dd15c3a6574032e9b1b92b148ab4e383599 - gerlowskija -
> 2024-02-07 15:10:39]
>at
> org.apache.solr.handler.admin.CollectionsHandler.invokeAction(CollectionsHandler.java:319)
> ~[solr-core-9.5.0.jar:9.5.0 c
> dd27dd15c3a6574032e9b1b92b148ab4e383599 - gerlowskija - 2024-02-07 15:10:39]
>at
> org.apache.solr.handler.admin.CollectionsHandler.handleRequestBody(CollectionsHandler.java:297)
> ~[solr-core-9.5.0.jar:9.
> 5.0 cdd27dd15c3a6574032e9b1b92b148ab4e383599 - gerlowskija - 2024-02-07
> 15:10:39]
>at
> org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:226)
> ~[solr-core-9.5.0.jar:9.5.0 cdd27d
> d15c3a6574032e9b1b92b

Solr 9.1.1 - Task queue processing

[Stoyanov, Nikolay]

Hello,
I am using solr 9.1.1 in cloud mode with two replicas on different VMs.



Lately we are experiencing issue with task queue processing.

I have read about the other similar issues and tried the mentioned  solutions 
but nothing managed to solve the issue.

Could you please assist me with what could be causing the issue and how to 
solve it.



Below you can find details from the exception.

java.io.IOException: Task queue processing has stalled for 20191 ms with 0 
remaining elements to process.
  at 
org.apache.solr.client.solrj.impl.ConcurrentUpdateHttp2SolrClient.blockUntilFinished(ConcurrentUpdateHttp2SolrClient.java:508)
  at 
org.apache.solr.update.StreamingSolrClients.blockUntilFinished(StreamingSolrClients.java:87)
  at 
org.apache.solr.update.SolrCmdDistributor.blockAndDoRetries(SolrCmdDistributor.java:292)
  at 
org.apache.solr.update.SolrCmdDistributor.finish(SolrCmdDistributor.java:91)
  at 
org.apache.solr.update.processor.DistributedZkUpdateProcessor.doDistribFinish(DistributedZkUpdateProcessor.java:1263)
  at 
org.apache.solr.update.processor.DistributedUpdateProcessor.finish(DistributedUpdateProcessor.java:1253)
  at 
org.apache.solr.update.processor.UpdateRequestProcessor.finish(UpdateRequestProcessor.java:78)
  at 
org.apache.solr.handler.ContentStreamHandlerBase.handleRequestBody(ContentStreamHandlerBase.java:94)
  at 
org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:224)
  at org.apache.solr.core.SolrCore.execute(SolrCore.java:2865)
  at org.apache.solr.servlet.HttpSolrCall.execute(HttpSolrCall.java:887)
  at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:606)
  at 
org.apache.solr.servlet.SolrDispatchFilter.dispatch(SolrDispatchFilter.java:250)
  at 
org.apache.solr.servlet.SolrDispatchFilter.lambda$doFilter$0(SolrDispatchFilter.java:218)
  at 
org.apache.solr.servlet.ServletUtils.traceHttpRequestExecution2(ServletUtils.java:257)
  at 
org.apache.solr.servlet.ServletUtils.rateLimitRequest(ServletUtils.java:227)
  at 
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:213)
  at 
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:195)
  at org.eclipse.jetty.servlet.FilterHolder.doFilter(FilterHolder.java:201)
  at 
org.eclipse.jetty.servlet.ServletHandler$Chain.doFilter(ServletHandler.java:1626)
  at 
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:552)
  at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
  at 
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:600)
  at 
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127)
  at 
org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:235)
  at 
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1624)
  at 
org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:233)
  at 
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1440)
  at 
org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:188)
  at 
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:505)
  at 
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1594)
  at 
org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:186)
  at 
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1355)
  at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
  at 
org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:191)
  at 
org.eclipse.jetty.server.handler.InetAccessHandler.handle(InetAccessHandler.java:177)
  at 
org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:146)
  at 
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127)
  at 
org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(RewriteHandler.java:322)
  at 
org.eclipse.jetty.server.handler.gzip.GzipHandler.handle(GzipHandler.java:772)
  at 
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127)
  at org.eclipse.jetty.server.Server.handle(Server.java:516)
  at 
org.eclipse.jetty.server.HttpChannel.lambda$handle$1(HttpChannel.java:487)
  at org.eclipse.jetty.server.HttpChannel.dispatch(HttpChannel.java:732)
  at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:479)
  at 
org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:277)
  at 
org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:311)
  at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:105)
  at org.eclipse.jetty.io.ChannelEndPoint$1.run(ChannelEndPoint.java:104)
 

Re: Solr-9.5 | collection creation error

[HariBabu kuruva]

Hi Jan,

Thanks for the response.

Please find the details below:

*Exactly how did you install Solr, and what is your ZK_HOST connection
string?:*
I got the solr-9.5.0.tg.zip file from Solr website and unzipped it.
ZK_HOST = "ZK_host1.corp.abc.com:3181,ZK_Host2.corp.abc.com:3182,
ZK_Host3.corp.equinbcax.com:3183"
- *Exactly how did you install ZK, and what is your zoo.cfg, on each of the
three nodes.*
 I have got the zip file and uninstalled it.
*zoo.cfg:*

*---*tickTime=2000
initLimit=10
syncLimit=5
4lw.commands.whitelist=*
dataDir=/gdev/zk1/zoo/data/1
clientPort=3181
autopurge.snapRetainCount=3
autopurge.purgeInterval=12
server.1=ZKHost1.corp.equinix.com:4888:5888
server.2=ZKHost2.corp.equinix.com:4889:5889
server.3=ZKHost3.corp.equinix.com:4890:5890
admin.serverPort=8081
---
*- Which command did you use to create the collection?*
---   Commands:   -
  update_command="/gdev/opt/eisp/solr-9.5.0/bin/solr zk -upconfig -z
$zoo_keeper_host -n $config_name -d
 /gdev/opt/eisp/solr/configsets/$store_name"
  create_command="curl -k --user solr:SolrRocks
'$solr_admin_url/solr/admin/collections?
action=CREATE&name=$store_name&numShards=1&replicationFactor=2&maxShardsPerNode=1&collection.configName=$config_name'"

*Note: *Configsets folder , i am using the same files of current running
version solr-8.11.1
---
-* Does this happen every time you try to create a collection, even if you
create a test collection with _default configset from the UI?*
*Yes, i can see the same error from UI also and also with _default
configset as well*

*- Did the Solr node crash or recover during this process?*
No
*- Are there ERRORs in Zookeeper's log files?*
No errors in ZK logs.

Please let me know if any other info is required.



On Wed, Apr 17, 2024 at 12:39 PM Jan Høydahl  wrote:

> Hi,
>
> Do you mind sharing the details with us?
>
> - Exactly how did you install Solr, and what is your ZK_HOST connection
> string?
> - Exactly how did you install ZK, and what is your zoo.cfg, on each of the
> three nodes.
> - Which command did you use to create the collection?
> - Does this happen every time you try to create a collection, even if you
> create a test collection with _default configset from the UI?
> - Did the Solr node crash or recover during this process?
> - Are there ERRORs in Zookeeper's log files?
>
> Jan
>
> > 17. apr. 2024 kl. 02:37 skrev HariBabu kuruva  >:
> >
> > HI ,  I am working on a POC, to set up solr-9.5.0. Currently I have
> > Solr-8.11.1 installed and running.
> >
> > As part of the POC. I have installed Solr-9.5.0(on one node) and
> Zookeeper
> > 3.9.2 (on 3 nodes). This setup is done on the same server where I have
> > solr-8.5 running but with different ports.
> >
> > Solr and Zookeeper are running on separate nodes and are running fine.
> >
> > When I try to create the collection using the below command. I get this
> > error. Please help me.
> >
> >
> >
> > 2024-04-16 05:17:09.045 ERROR (OverseerThreadFactory-17-thread-5)
> [c:test1
> > s: r: x: t:] o.a.s.c.a.c.CollectionHandlingUtils Collect
> > ion test1, operation create failed =>
> org.apache.solr.common.SolrException:
> > Underlying core creation failed while creating collecti
> > on: test1
> >at
> >
> org.apache.solr.cloud.api.collections.CreateCollectionCmd.call(CreateCollectionCmd.java:447)
> > org.apache.solr.common.SolrException: Underlying core creation failed
> while
> > creating collection: test1
> >at
> >
> org.apache.solr.cloud.api.collections.CreateCollectionCmd.call(CreateCollectionCmd.java:447)
> > ~[solr-core-9.5.0.jar:9.5.0
> > cdd27dd15c3a6574032e9b1b92b148ab4e383599 - gerlowskija - 2024-02-07
> > 15:10:39]
> >at
> >
> org.apache.solr.cloud.api.collections.CollApiCmds$TraceAwareCommand.call(CollApiCmds.java:225)
> > ~[solr-core-9.5.0.jar:9.5
> > .0 cdd27dd15c3a6574032e9b1b92b148ab4e383599 - gerlowskija - 2024-02-07
> > 15:10:39]
> >at
> >
> org.apache.solr.cloud.api.collections.OverseerCollectionMessageHandler.processMessage(OverseerCollectionMessageHandler.j
> > ava:130) ~[solr-core-9.5.0.jar:9.5.0
> > cdd27dd15c3a6574032e9b1b92b148ab4e383599 - gerlowskija - 2024-02-07
> > 15:10:39]
> >at
> >
> org.apache.solr.cloud.OverseerTaskProcessor$Runner.run(OverseerTaskProcessor.java:564)
> > ~[solr-core-9.5.0.jar:9.5.0 cdd27
> > dd15c3a6574032e9b1b92b148ab4e383599 - gerlowskija - 2024-02-07 15:10:39]
> >at
> >
> org.apache.solr.common.util.ExecutorUtil$MDCAwareThreadPoolExecutor.lambda$execute$0(ExecutorUtil.java:299)
> > ~[solr-solrj
> > -9.5.0.jar:9.5.0 cdd27dd15c3a6574032e9b1b92b148ab4e383599 - gerlowskija -
> > 2024-02-07 15:10:39]
> >at
> >
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> > ~[?:?]
> >at
> >
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> > ~[?:?]
> >at java.

Re: Solr 9.1.1 - Task queue processing

[HariBabu kuruva]

Hi,

Can you please try increasing stalltime by adding the below parameter in
the startup script.

*-Dsolr.cloud.client.stallTime=6*

Also try to analyze the indexing load on the solr nodes and see if you can
reduce it.

On Wed, Apr 17, 2024 at 1:58 PM Stoyanov, Nikolay
 wrote:

> Hello,
> I am using solr 9.1.1 in cloud mode with two replicas on different VMs.
>
>
>
> Lately we are experiencing issue with task queue processing.
>
> I have read about the other similar issues and tried the mentioned
> solutions but nothing managed to solve the issue.
>
> Could you please assist me with what could be causing the issue and how to
> solve it.
>
>
>
> Below you can find details from the exception.
>
> java.io.IOException: Task queue processing has stalled for 20191 ms with 0
> remaining elements to process.
> at
> org.apache.solr.client.solrj.impl.ConcurrentUpdateHttp2SolrClient.blockUntilFinished(ConcurrentUpdateHttp2SolrClient.java:508)
> at
> org.apache.solr.update.StreamingSolrClients.blockUntilFinished(StreamingSolrClients.java:87)
> at
> org.apache.solr.update.SolrCmdDistributor.blockAndDoRetries(SolrCmdDistributor.java:292)
> at
> org.apache.solr.update.SolrCmdDistributor.finish(SolrCmdDistributor.java:91)
> at
> org.apache.solr.update.processor.DistributedZkUpdateProcessor.doDistribFinish(DistributedZkUpdateProcessor.java:1263)
> at
> org.apache.solr.update.processor.DistributedUpdateProcessor.finish(DistributedUpdateProcessor.java:1253)
> at
> org.apache.solr.update.processor.UpdateRequestProcessor.finish(UpdateRequestProcessor.java:78)
> at
> org.apache.solr.handler.ContentStreamHandlerBase.handleRequestBody(ContentStreamHandlerBase.java:94)
> at
> org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:224)
> at org.apache.solr.core.SolrCore.execute(SolrCore.java:2865)
> at org.apache.solr.servlet.HttpSolrCall.execute(HttpSolrCall.java:887)
> at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:606)
> at
> org.apache.solr.servlet.SolrDispatchFilter.dispatch(SolrDispatchFilter.java:250)
> at
> org.apache.solr.servlet.SolrDispatchFilter.lambda$doFilter$0(SolrDispatchFilter.java:218)
> at
> org.apache.solr.servlet.ServletUtils.traceHttpRequestExecution2(ServletUtils.java:257)
> at
> org.apache.solr.servlet.ServletUtils.rateLimitRequest(ServletUtils.java:227)
> at
> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:213)
> at
> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:195)
> at org.eclipse.jetty.servlet.FilterHolder.doFilter(FilterHolder.java:201)
> at
> org.eclipse.jetty.servlet.ServletHandler$Chain.doFilter(ServletHandler.java:1626)
> at
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:552)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
> at
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:600)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:235)
> at
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1624)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:233)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1440)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:188)
> at
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:505)
> at
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1594)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:186)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1355)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
> at
> org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:191)
> at
> org.eclipse.jetty.server.handler.InetAccessHandler.handle(InetAccessHandler.java:177)
> at
> org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:146)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127)
> at
> org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(RewriteHandler.java:322)
> at
> org.eclipse.jetty.server.handler.gzip.GzipHandler.handle(GzipHandler.java:772)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127)
> at org.eclipse.jetty.server.Server.handle(Server.java:516)
> at
> org.eclipse.jetty.server.HttpChannel.lambda$handle$1(HttpChannel.java:487)
> at org.eclipse.jetty.server.HttpChannel.dispatch(HttpChannel.java:732)
> at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:479)
> at
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:277)
> at org.eclipse.jetty.io
> .AbstractConnection$ReadCallback.succeeded(AbstractConnection.ja

Re: Solr 9.1.1 - Task queue processing

[Mikhail Khludnev]

It might seem like a target node took more than 20 sec for commit.
Since remaining elems are 0, it's worth checking the next side node logs
for any errors and hiccups.

On Wed, Apr 17, 2024 at 11:24 AM Stoyanov, Nikolay
 wrote:

> Hello,
> I am using solr 9.1.1 in cloud mode with two replicas on different VMs.
>
>
>
> Lately we are experiencing issue with task queue processing.
>
> I have read about the other similar issues and tried the mentioned
> solutions but nothing managed to solve the issue.
>
> Could you please assist me with what could be causing the issue and how to
> solve it.
>
>
>
> Below you can find details from the exception.
>
> java.io.IOException: Task queue processing has stalled for 20191 ms with 0
> remaining elements to process.
> at
> org.apache.solr.client.solrj.impl.ConcurrentUpdateHttp2SolrClient.blockUntilFinished(ConcurrentUpdateHttp2SolrClient.java:508)
> at
> org.apache.solr.update.StreamingSolrClients.blockUntilFinished(StreamingSolrClients.java:87)
> at
> org.apache.solr.update.SolrCmdDistributor.blockAndDoRetries(SolrCmdDistributor.java:292)
> at
> org.apache.solr.update.SolrCmdDistributor.finish(SolrCmdDistributor.java:91)
> at
> org.apache.solr.update.processor.DistributedZkUpdateProcessor.doDistribFinish(DistributedZkUpdateProcessor.java:1263)
> at
> org.apache.solr.update.processor.DistributedUpdateProcessor.finish(DistributedUpdateProcessor.java:1253)
> at
> org.apache.solr.update.processor.UpdateRequestProcessor.finish(UpdateRequestProcessor.java:78)
> at
> org.apache.solr.handler.ContentStreamHandlerBase.handleRequestBody(ContentStreamHandlerBase.java:94)
> at
> org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:224)
> at org.apache.solr.core.SolrCore.execute(SolrCore.java:2865)
> at org.apache.solr.servlet.HttpSolrCall.execute(HttpSolrCall.java:887)
> at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:606)
> at
> org.apache.solr.servlet.SolrDispatchFilter.dispatch(SolrDispatchFilter.java:250)
> at
> org.apache.solr.servlet.SolrDispatchFilter.lambda$doFilter$0(SolrDispatchFilter.java:218)
> at
> org.apache.solr.servlet.ServletUtils.traceHttpRequestExecution2(ServletUtils.java:257)
> at
> org.apache.solr.servlet.ServletUtils.rateLimitRequest(ServletUtils.java:227)
> at
> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:213)
> at
> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:195)
> at org.eclipse.jetty.servlet.FilterHolder.doFilter(FilterHolder.java:201)
> at
> org.eclipse.jetty.servlet.ServletHandler$Chain.doFilter(ServletHandler.java:1626)
> at
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:552)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
> at
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:600)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:235)
> at
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1624)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:233)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1440)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:188)
> at
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:505)
> at
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1594)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:186)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1355)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
> at
> org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:191)
> at
> org.eclipse.jetty.server.handler.InetAccessHandler.handle(InetAccessHandler.java:177)
> at
> org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:146)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127)
> at
> org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(RewriteHandler.java:322)
> at
> org.eclipse.jetty.server.handler.gzip.GzipHandler.handle(GzipHandler.java:772)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127)
> at org.eclipse.jetty.server.Server.handle(Server.java:516)
> at
> org.eclipse.jetty.server.HttpChannel.lambda$handle$1(HttpChannel.java:487)
> at org.eclipse.jetty.server.HttpChannel.dispatch(HttpChannel.java:732)
> at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:479)
> at
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:277)
> at org.eclipse.jetty.io
> .AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:311)
> at org.eclipse.jetty.io.FillInterest.fillable

docValues true is not working for solr.TextField in Solr 8.9.0

[Vishal Patel]

We are using Solr 8.9.0. We have configured Solr cloud like 2 shards and each 
shard has one replica. We have used 7 zoo keepers for Solr cloud.
Our schema field is like



  


  
  


  


We are using sorting and faceting on both field title and AIR_ts_s_100. We see 
the both field in fieldCache using admin panel and it is taking much memory. 
After the long time it is not decreasing.
We know the we can not apply docValues true directly in solr.TextField. So, We 
have taken reference from https://github.com/grossws/solr-dvtf.

It is working fine for title like after applying sort and facet on title field 
we can not see in fieldCache but when we are applying sort on AIR_ts_s_100 then 
we are getting ERROR
org.apache.solr.common.SolrException: can not sort on multivalued field: 
AIR_ts_s_100 of type: text_string
  at 
org.apache.solr.schema.SchemaField.checkSortability(SchemaField.java:188)
  at 
org.apache.solr.schema.FieldType.getSortedSetSortField(FieldType.java:732)
  at org.apache.solr.schema.TextField.getSortField(TextField.java:121)
  at org.apache.solr.schema.SchemaField.getSortField(SchemaField.java:154)
  
Can you please suggest us why we are getting ERROR like can not sort on 
multivalued field? because it is not multi value true.

Our main issue is day by day increasing the fieldCache size. How can we avoid 
or reduce size for solr.TextField?

Regards,
Vishal

Re: Problem with word separators?

[Carsten Klement]

Hello, doesn't anyone have an idea? ☹



Am 10.04.24, 11:40 schrieb "Carsten Klement" mailto:kont...@carsten-klement.de>>:


Hello,
I think I have a problem with configured Word separators.

For example, I would like 3 items to be found when searching for 640, 640-0 and 
two when searching for 640-01.

#1
artikelnummer_txt:"640*" AND lng:"de"
"docs":[{
"artikelnummer_txt":"640-01"
},{
"artikelnummer_txt":"640-02"
},{
"artikelnummer_txt":"640-01LFM"
}]

This is perfect, everything from the “artikelnummer_txt” field that starts with 
640 will be found.

#2 
artikelnummer_txt:"640-0*" AND lng:"de"
"docs":[ ]


However, if I enter a "-" with a "0", no article is found. Here I expect all 
three items


#3
artikelnummer_txt:"640-01*" AND lng:"de"
"docs":[{
"artikelnummer_txt":"640-01"
}]

Here I only get one item, but I also expect two items.

My configuration in schema.xml




















### wordDelimiters.txt
# Don't split numbers at '$', '.' or ','
$ => DIGIT
. => DIGIT
- => ALPHANUM 


Maybe someone has an idea what I'm doing wrong?

Thanks
Carsten

Re: Solr 9.1.1 - Task queue processing

[Stoyanov, Nikolay]

Hello,

There are no exceptions/errors on the other node.

Best regards,
Nikolay

From: Mikhail Khludnev 
Sent: Wednesday, April 17, 2024 1:07 PM
To: users@solr.apache.org 
Subject: Re: Solr 9.1.1 - Task queue processing

It might seem like a target node took more than 20 sec for commit.
Since remaining elems are 0, it's worth checking the next side node logs
for any errors and hiccups.

On Wed, Apr 17, 2024 at 11:24 AM Stoyanov, Nikolay
 wrote:

> Hello,
> I am using solr 9.1.1 in cloud mode with two replicas on different VMs.
>
>
>
> Lately we are experiencing issue with task queue processing.
>
> I have read about the other similar issues and tried the mentioned
> solutions but nothing managed to solve the issue.
>
> Could you please assist me with what could be causing the issue and how to
> solve it.
>
>
>
> Below you can find details from the exception.
>
> java.io.IOException: Task queue processing has stalled for 20191 ms with 0
> remaining elements to process.
> at
> org.apache.solr.client.solrj.impl.ConcurrentUpdateHttp2SolrClient.blockUntilFinished(ConcurrentUpdateHttp2SolrClient.java:508)
> at
> org.apache.solr.update.StreamingSolrClients.blockUntilFinished(StreamingSolrClients.java:87)
> at
> org.apache.solr.update.SolrCmdDistributor.blockAndDoRetries(SolrCmdDistributor.java:292)
> at
> org.apache.solr.update.SolrCmdDistributor.finish(SolrCmdDistributor.java:91)
> at
> org.apache.solr.update.processor.DistributedZkUpdateProcessor.doDistribFinish(DistributedZkUpdateProcessor.java:1263)
> at
> org.apache.solr.update.processor.DistributedUpdateProcessor.finish(DistributedUpdateProcessor.java:1253)
> at
> org.apache.solr.update.processor.UpdateRequestProcessor.finish(UpdateRequestProcessor.java:78)
> at
> org.apache.solr.handler.ContentStreamHandlerBase.handleRequestBody(ContentStreamHandlerBase.java:94)
> at
> org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:224)
> at org.apache.solr.core.SolrCore.execute(SolrCore.java:2865)
> at org.apache.solr.servlet.HttpSolrCall.execute(HttpSolrCall.java:887)
> at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:606)
> at
> org.apache.solr.servlet.SolrDispatchFilter.dispatch(SolrDispatchFilter.java:250)
> at
> org.apache.solr.servlet.SolrDispatchFilter.lambda$doFilter$0(SolrDispatchFilter.java:218)
> at
> org.apache.solr.servlet.ServletUtils.traceHttpRequestExecution2(ServletUtils.java:257)
> at
> org.apache.solr.servlet.ServletUtils.rateLimitRequest(ServletUtils.java:227)
> at
> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:213)
> at
> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:195)
> at org.eclipse.jetty.servlet.FilterHolder.doFilter(FilterHolder.java:201)
> at
> org.eclipse.jetty.servlet.ServletHandler$Chain.doFilter(ServletHandler.java:1626)
> at
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:552)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
> at
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:600)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:235)
> at
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1624)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:233)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1440)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:188)
> at
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:505)
> at
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1594)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:186)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1355)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
> at
> org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:191)
> at
> org.eclipse.jetty.server.handler.InetAccessHandler.handle(InetAccessHandler.java:177)
> at
> org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:146)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127)
> at
> org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(RewriteHandler.java:322)
> at
> org.eclipse.jetty.server.handler.gzip.GzipHandler.handle(GzipHandler.java:772)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127)
> at org.eclipse.jetty.server.Server.handle(Server.java:516)
> at
> org.eclipse.jetty.server.HttpChannel.lambda$handle$1(HttpChannel.java:487)
> at org.eclipse.jetty.server.HttpChannel.dispatch(HttpChannel.java:732)
> at org.eclipse.jetty.server.HttpChannel.handl

Re: Problem with word separators?

[Benjamin Armintor]

I don’t use that graph filter, but from the documentation it looks like a
couple of other splitters may still be affecting those tokens (like
splitOnCaseChange, splitOnNumerics, generateNumberParts).

Some of the apparent complexity here is using text-oriented fields and
tokenizers but trying to capture what appear to be structured article
identifiers. If you are specifically trying to find these in text content,
you might be better served by a different tokenizer (maybe even the
ClassicTokenizer) or a regex matcher.

If you don’t actually need to find those numbers in text, you might be
better served by using a plain string index field?

On Wed, Apr 17, 2024 at 8:43 AM Carsten Klement 
wrote:

> Hello, doesn't anyone have an idea? ☹
>
>
>
> Am 10.04.24, 11:40 schrieb "Carsten Klement"  >:
>
>
> Hello,
> I think I have a problem with configured Word separators.
>
> For example, I would like 3 items to be found when searching for 640,
> 640-0 and two when searching for 640-01.
>
> #1
> artikelnummer_txt:"640*" AND lng:"de"
> "docs":[{
> "artikelnummer_txt":"640-01"
> },{
> "artikelnummer_txt":"640-02"
> },{
> "artikelnummer_txt":"640-01LFM"
> }]
>
> This is perfect, everything from the “artikelnummer_txt” field that starts
> with 640 will be found.
>
> #2
> artikelnummer_txt:"640-0*" AND lng:"de"
> "docs":[ ]
>
>
> However, if I enter a "-" with a "0", no article is found. Here I expect
> all three items
>
>
> #3
> artikelnummer_txt:"640-01*" AND lng:"de"
> "docs":[{
> "artikelnummer_txt":"640-01"
> }]
>
> Here I only get one item, but I also expect two items.
>
> My configuration in schema.xml
>  stored="true"/>
>  positionIncrementGap="100" multiValued="false">
> 
> 
> 
> 
> 
>
> 
> 
> 
> 
> 
> 
> 
>  expand="true"/>
> 
> 
> 
>
> ### wordDelimiters.txt
> # Don't split numbers at '$', '.' or ','
> $ => DIGIT
> . => DIGIT
> - => ALPHANUM
>
>
> Maybe someone has an idea what I'm doing wrong?
>
> Thanks
> Carsten
>
>
>
>
>
>
>
>
>
>

Re: Problem with word separators?

[Mikhail Khludnev]

Check how query is parsed via debugQuery
Also check how analysis handles these string - there's a page in slr admin
to examine it.

On Wed, Apr 17, 2024 at 3:43 PM Carsten Klement 
wrote:

> Hello, doesn't anyone have an idea? ☹
>
>
>
> Am 10.04.24, 11:40 schrieb "Carsten Klement"  >:
>
>
> Hello,
> I think I have a problem with configured Word separators.
>
> For example, I would like 3 items to be found when searching for 640,
> 640-0 and two when searching for 640-01.
>
> #1
> artikelnummer_txt:"640*" AND lng:"de"
> "docs":[{
> "artikelnummer_txt":"640-01"
> },{
> "artikelnummer_txt":"640-02"
> },{
> "artikelnummer_txt":"640-01LFM"
> }]
>
> This is perfect, everything from the “artikelnummer_txt” field that starts
> with 640 will be found.
>
> #2
> artikelnummer_txt:"640-0*" AND lng:"de"
> "docs":[ ]
>
>
> However, if I enter a "-" with a "0", no article is found. Here I expect
> all three items
>
>
> #3
> artikelnummer_txt:"640-01*" AND lng:"de"
> "docs":[{
> "artikelnummer_txt":"640-01"
> }]
>
> Here I only get one item, but I also expect two items.
>
> My configuration in schema.xml
>  stored="true"/>
>  positionIncrementGap="100" multiValued="false">
> 
> 
> 
> 
> 
>
> 
> 
> 
> 
> 
> 
> 
>  expand="true"/>
> 
> 
> 
>
> ### wordDelimiters.txt
> # Don't split numbers at '$', '.' or ','
> $ => DIGIT
> . => DIGIT
> - => ALPHANUM
>
>
> Maybe someone has an idea what I'm doing wrong?
>
> Thanks
> Carsten
>
>
>
>
>
>
>
>
>
>

-- 
Sincerely yours
Mikhail Khludnev

Invalid JSON on solr9 when using a binary field

[Karl Stoney]

Hi,
I’m currently looking into the solr 8 -> solr 9 upgrade, and we’ve noticed that 
if a document is using a binary field, the json returned is invalid because the 
value is not quoted:

For example on solr 8 we’d see:

```
"STOCK_ITEM_BINARY_FIELD":”OikKAfqEdXJzSWRjNTEwMj…”
```

But on solr 8 we get back:

```
"STOCK_ITEM_BINARY_FIELD":OikKAfqEdXJzSWRjNTEwMj…
```

(note both these examples are observed through the Solr UI too):

This feels like a bug, but wanted to check here before I raised it as one?


Unless expressly stated otherwise in this email, this e-mail is sent on behalf 
of Auto Trader Limited Registered Office: 1 Tony Wilson Place, Manchester, 
Lancashire, M15 4FN (Registered in England No. 03909628). Auto Trader Limited 
is part of the Auto Trader Group Plc group. This email and any files 
transmitted with it are confidential and may be legally privileged, and 
intended solely for the use of the individual or entity to whom they are 
addressed. If you have received this email in error please notify the sender. 
This email message has been swept for the presence of computer viruses.

Error installing solr-8.11.3 on RHEL 9.3

[Johnnie W Adams]

Hi, folks,

 I've hit some errors on attempting this install:

./install_solr_service.sh solr-8.11.3.tgz -i
/u01/app/svc_archivesspace/solr-8.11.3 -u svc_archivesspace


Extracting solr-8.11.3.tgz to /u01/app/svc_archivesspace/solr-8.11.3



Installing symlink /u01/app/svc_archivesspace/solr-8.11.3/solr ->
/u01/app/svc_archivesspace/solr-8.11.3/solr-8.11.3 ...



Installing /etc/init.d/solr script ...


cp: cannot create regular file '/etc/init.d/solr': No such file or directory

chmod: cannot access '/etc/init.d/solr': No such file or directory

chown: cannot access '/etc/init.d/solr': No such file or directory

sed: can't read /etc/init.d/solr: No such file or directory


Installing /etc/default/solr.in.sh ...


./install_solr_service.sh: line 356: chkconfig: command not found

Service solr installed.

Customize Solr startup configuration in /etc/default/solr.in.sh

Redirecting to /bin/systemctl start solr.service

*Failed to start solr.service: Unit solr.service not found.*

Redirecting to /bin/systemctl status solr.service

*Unit solr.service could not be found.*

 It looks like the install script is assuming that chkconfig is going
to do some work for it, but chkconfig is not there to do it. It would also
like for /etc/init.d to pre-exist.

 Your thoughts?

Thanks,

 John A

-- 
John Adams
Senior Linux/Middleware Administrator  | Information Technology Services
+1-501-916-3010 | jxad...@ualr.edu | http://ualr.edu/itservices
*UA Little Rock*

Reminder:  IT Services will never ask for your password over the phone or
in an email. Always be suspicious of requests for personal information that
come via email, even from known contacts.  For more information or to
report suspicious email, visit IT Security
.

Re: Invalid JSON on solr9 when using a binary field

[Thomas Corthals]

Hi Karl,

What is the exact version of Solr 9 you're trying to upgrade to?

This sounds very similar to this issue:
https://lists.apache.org/list?users@solr.apache.org:gte=0d:&header_subject=Invalid%20JSON%20response%20with%20UUID%20field

Thomas

Op wo 17 apr 2024 om 16:55 schreef Karl Stoney
:

> Hi,
> I’m currently looking into the solr 8 -> solr 9 upgrade, and we’ve noticed
> that if a document is using a binary field, the json returned is invalid
> because the value is not quoted:
>
> For example on solr 8 we’d see:
>
> ```
> "STOCK_ITEM_BINARY_FIELD":”OikKAfqEdXJzSWRjNTEwMj…”
> ```
>
> But on solr 8 we get back:
>
> ```
> "STOCK_ITEM_BINARY_FIELD":OikKAfqEdXJzSWRjNTEwMj…
> ```
>
> (note both these examples are observed through the Solr UI too):
>
> This feels like a bug, but wanted to check here before I raised it as one?
>
>
> Unless expressly stated otherwise in this email, this e-mail is sent on
> behalf of Auto Trader Limited Registered Office: 1 Tony Wilson Place,
> Manchester, Lancashire, M15 4FN (Registered in England No. 03909628). Auto
> Trader Limited is part of the Auto Trader Group Plc group. This email and
> any files transmitted with it are confidential and may be legally
> privileged, and intended solely for the use of the individual or entity to
> whom they are addressed. If you have received this email in error please
> notify the sender. This email message has been swept for the presence of
> computer viruses.
>

Re: Error installing solr-8.11.3 on RHEL 9.3

[Dmitri Maziuk]

On 4/17/24 10:43, Johnnie W Adams wrote:

Hi, folks,

...

  It looks like the install script is assuming that chkconfig is going
to do some work for it, but chkconfig is not there to do it. It would also
like for /etc/init.d to pre-exist.

  Your thoughts?


Ditch DeadRat, use Alpine. Or some other lennart-free distro.

On a more serious note, the install script is obviously broken: it 
returns "success" after failing to create solr.service script for 
systemd. That may or may not have something to do with the absence of 
chkconfig and/or /etc/init.d.


Dima

Possibly bogus WARNings on startup

[Johnnie W Adams]

Hi, folks,

 I worked around (for the moment) my install problems and get this
message on starting solr up:

*** [WARN] *** Your open file limit is currently 1024.

 It should be set to 65000 to avoid operational disruption.

 If you no longer wish to see this warning, set SOLR_ULIMIT_CHECKS to false
in your profile or solr.in.sh

*** [WARN] ***  Your Max Processes Limit is currently 14430.

 It should be set to 65000 to avoid operational disruption.

 If you no longer wish to see this warning, set SOLR_ULIMIT_CHECKS to false
in your profile or solr.in.sh


 However:

# sysctl -p

fs.file-max = 65000

kernel.pid_max = 65000

 Are these WARNings accurate? I guess I could just disable them, but
that seems sloppy.

Thanks,

 John A
-- 
John Adams
Senior Linux/Middleware Administrator  | Information Technology Services
+1-501-916-3010 | jxad...@ualr.edu | http://ualr.edu/itservices
*UA Little Rock*

Reminder:  IT Services will never ask for your password over the phone or
in an email. Always be suspicious of requests for personal information that
come via email, even from known contacts.  For more information or to
report suspicious email, visit IT Security
.

Re: Possibly bogus WARNings on startup

[Arrieta, Alejandro]

Hello,

With Solr already started.
#get solr pid
ps -ef|grep solr
#list process limits
cat /proc/solrpid/limits

As the user that runs Solr you can check the user limits:
#hard limits
ulimit -Ha
#soft limits
ulimit -Sa

Generally, the soft limits are applied.
You can change them in /etc/security/limits.d/solr.conf
as described here:
https://www.searchistheway.com/posts/How_to_help_Apache_Solr_project_testing_Solr_9.5.RC3/#setting-user-limits

Hope this helps

Kind regards,
Alejandro Arrieta




On Wed, Apr 17, 2024 at 1:32 PM Johnnie W Adams  wrote:

> Hi, folks,
>
>  I worked around (for the moment) my install problems and get this
> message on starting solr up:
>
> *** [WARN] *** Your open file limit is currently 1024.
>
>  It should be set to 65000 to avoid operational disruption.
>
>  If you no longer wish to see this warning, set SOLR_ULIMIT_CHECKS to false
> in your profile or solr.in.sh
>
> *** [WARN] ***  Your Max Processes Limit is currently 14430.
>
>  It should be set to 65000 to avoid operational disruption.
>
>  If you no longer wish to see this warning, set SOLR_ULIMIT_CHECKS to false
> in your profile or solr.in.sh
>
>
>  However:
>
> # sysctl -p
>
> fs.file-max = 65000
>
> kernel.pid_max = 65000
>
>  Are these WARNings accurate? I guess I could just disable them, but
> that seems sloppy.
>
> Thanks,
>
>  John A
> --
> John Adams
> Senior Linux/Middleware Administrator  | Information Technology Services
> +1-501-916-3010 | jxad...@ualr.edu | http://ualr.edu/itservices
> *UA Little Rock*
>
> Reminder:  IT Services will never ask for your password over the phone or
> in an email. Always be suspicious of requests for personal information that
> come via email, even from known contacts.  For more information or to
> report suspicious email, visit IT Security
> .
>

Max value for maxBooleanClauses?

[Walter Underwood]

Is there a hard upper limit for maxBooleanClauses? We have someone hitting a 
limit at 64k clauses after upgrading to 9.x.

wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/  (my blog)

Re: Error installing solr-8.11.3 on RHEL 9.3

[Jan Høydahl]

Hi,

I believe RHEL uses systemd, so you'll have to first install the package for 
initd, I cannot remember the yum name now. Then try the install script again.

Jan

> 17. apr. 2024 kl. 17:43 skrev Johnnie W Adams :
> 
> Hi, folks,
> 
> I've hit some errors on attempting this install:
> 
> ./install_solr_service.sh solr-8.11.3.tgz -i
> /u01/app/svc_archivesspace/solr-8.11.3 -u svc_archivesspace
> 
> 
> Extracting solr-8.11.3.tgz to /u01/app/svc_archivesspace/solr-8.11.3
> 
> 
> 
> Installing symlink /u01/app/svc_archivesspace/solr-8.11.3/solr ->
> /u01/app/svc_archivesspace/solr-8.11.3/solr-8.11.3 ...
> 
> 
> 
> Installing /etc/init.d/solr script ...
> 
> 
> cp: cannot create regular file '/etc/init.d/solr': No such file or directory
> 
> chmod: cannot access '/etc/init.d/solr': No such file or directory
> 
> chown: cannot access '/etc/init.d/solr': No such file or directory
> 
> sed: can't read /etc/init.d/solr: No such file or directory
> 
> 
> Installing /etc/default/solr.in.sh ...
> 
> 
> ./install_solr_service.sh: line 356: chkconfig: command not found
> 
> Service solr installed.
> 
> Customize Solr startup configuration in /etc/default/solr.in.sh
> 
> Redirecting to /bin/systemctl start solr.service
> 
> *Failed to start solr.service: Unit solr.service not found.*
> 
> Redirecting to /bin/systemctl status solr.service
> 
> *Unit solr.service could not be found.*
> 
> It looks like the install script is assuming that chkconfig is going
> to do some work for it, but chkconfig is not there to do it. It would also
> like for /etc/init.d to pre-exist.
> 
> Your thoughts?
> 
> Thanks,
> 
> John A
> 
> -- 
> John Adams
> Senior Linux/Middleware Administrator  | Information Technology Services
> +1-501-916-3010 | jxad...@ualr.edu | http://ualr.edu/itservices
> *UA Little Rock*
> 
> Reminder:  IT Services will never ask for your password over the phone or
> in an email. Always be suspicious of requests for personal information that
> come via email, even from known contacts.  For more information or to
> report suspicious email, visit IT Security
> .

Re: Error installing solr-8.11.3 on RHEL 9.3

[Dmitri Maziuk]

On 4/17/24 15:47, Jan Høydahl wrote:

Hi,

I believe RHEL uses systemd, so you'll have to first install the package for 
initd, I cannot remember the yum name now. Then try the install script again.

Apparently on RHEL 9 it's initiscripts, initsctripts-service, and 
chkconfig. However,


"""
While RHEL 7 and higher use systemd moving forward, initscripts packages 
are still provided for the sole purpose of supporting legacy Red Hat 
provided scripts only. It is NOT intended to be used for 3rd party init 
scripts, and doing so can cause problems on the system such as boot 
failures or service failures. Additionally, 3rd party scripts are not 
covered by Red Hat's scope of support. The functionality therefore 
exists, but using it with 3rd party legacy init scripts is not supported.


We cannot guarantee that any 3rd party legacy init scripts will function 
as intended due to the nature of how systemd works with sysvinit, and 
cannot guarantee those scripts will work in the future. Ultimately it is 
recommended to contact the vendor that provides these scripts and ask 
them to provide proper systemd service units...

"""

https://access.redhat.com/solutions/7030065

Dima

Re: Max value for maxBooleanClauses?

[Chris Hostetter]

: Is there a hard upper limit for maxBooleanClauses? We have someone hitting a 
limit at 64k clauses after upgrading to 9.x.

There are two limits, one per-collection in solrconfig.xml that applies 
to query parsing, and one global in solr.xml that applies to every query 
including query expansion that hapens during query rewrite -- but those 
have both existed since at least 8.1

What did change in 9.0 is that the global limit now enforced recursively 
(by Lucene's index searcher) ...

https://solr.apache.org/guide/solr/latest/upgrade-notes/major-changes-in-solr-9.html#querying-and-indexing-2
https://solr.apache.org/guide/solr/latest/configuration-guide/configuring-solr-xml.html#global-maxbooleanclauses
https://solr.apache.org/guide/solr/latest/configuration-guide/caches-warming.html#maxbooleanclauses-element



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

Re: solr 9.2.1 plugin newSearcher function not called

[Chris Hostetter]

I'm really confused by your question -- you start off asking about 
AbstractSolrEventListener and the newSearcher event, but then when you 
show us your solrconfig.xml & plugin snippet you are showing us a usage of 
ValueSourceParser -- which doesn't exitend AbstractSolrEventListener -- 
and your question seems to be about ValueSourceParser.init() being called 
w/o the arguments you expect.

Can you explain in more depth what it is you are doing and what you expect 
to happen?  (Can you show us your full config + "working" unit test so we 
can understand what you _expect_ to happen in solr)


Generally speaking: Solr only fires "newSearcher" events for plugins that 
are registered as "newSearcher listeners" in solrconfig.xml, something 
like this...


  
solrprice asc
rocksweight asc
  


...a custom ValueSourceParser registered via  is 
completely ignorant of any newSearcher events -- it will be init()ed once 
during SolrCore init -- and should recieve the args specified in 
solrconfig.xml -- and the parse() will be called each time it is needed.  
If you need information about the SolrIndexSearcher at parse time, you can 
get it from the FunctionQParser (argument) via getReq().getSearcher()




: Date: Tue, 16 Apr 2024 12:11:41 +0200
: From: elisabeth benoit 
: Reply-To: users@solr.apache.org
: To: users@solr.apache.org
: Subject: solr 9.2.1 plugin newSearcher function not called
: 
: Hello,
: 
: We have a solr plugin with parameters in solrconfig.xml.
: 
: In the plugin, we use the newSearcher  function of a class overriding
: 
: AbstractSolrEventListener
: 
: to read parameters written in solrconfig.xml.
: 
: The plugin is working fine but the plugin function newSearcher is not
: called, so we cant read the parameters.
: 
: In unit test it's working, but not at runtime, I cant understand why.
: 
: I've tried another solution that I found in an example in solr source code
: 
: in solrconfig.xml in solr source code
: 
: 0.0
: 
: 
: 
: text
: 
: 
: 
: 
: reading the values in solr source code
: 
: public class NvlValueSourceParser extends ValueSourceParser {
: 
: /** Value to consider "null" when found in a ValueSource Defaults to 0.0 */
: private float nvlFloatValue = 0.0f;
: 
: 
: @Override
: public void init(NamedList args) {
: /* initialize the value to consider as null */
: Float nvlFloatValueArg = (Float) args.get("nvlFloatValue");
: if (nvlFloatValueArg != null) {
: this.nvlFloatValue = nvlFloatValueArg;
: }
: }
: }
: 
: when I do the same in my plugin code, when (in unit tests) code enters init
: function, args is empty.
: 
: Any help would be welcome!
: 
: Best regards,
: Elisabeth
: 

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

Re: Error installing solr-8.11.3 on RHEL 9.3

[Jan Høydahl]

Yes that were the packages, thanks.

If you are uncomfortable using init script on RHEL, you can always borrow the 
installer-script from Solr's git repository's main branch (to become version 
10.0), which uses systemd. You'd need to copy the install script and the 
systemd file and I think you should be able to make it work for Solr 9.x.

Jan

> 17. apr. 2024 kl. 23:22 skrev Dmitri Maziuk :
> 
> On 4/17/24 15:47, Jan Høydahl wrote:
>> Hi,
>> I believe RHEL uses systemd, so you'll have to first install the package for 
>> initd, I cannot remember the yum name now. Then try the install script again.
>> 
> Apparently on RHEL 9 it's initiscripts, initsctripts-service, and chkconfig. 
> However,
> 
> """
> While RHEL 7 and higher use systemd moving forward, initscripts packages are 
> still provided for the sole purpose of supporting legacy Red Hat provided 
> scripts only. It is NOT intended to be used for 3rd party init scripts, and 
> doing so can cause problems on the system such as boot failures or service 
> failures. Additionally, 3rd party scripts are not covered by Red Hat's scope 
> of support. The functionality therefore exists, but using it with 3rd party 
> legacy init scripts is not supported.
> 
> We cannot guarantee that any 3rd party legacy init scripts will function as 
> intended due to the nature of how systemd works with sysvinit, and cannot 
> guarantee those scripts will work in the future. Ultimately it is recommended 
> to contact the vendor that provides these scripts and ask them to provide 
> proper systemd service units...
> """
> 
> https://access.redhat.com/solutions/7030065
> 
> Dima
> 

Re: Max value for maxBooleanClauses?

[Walter Underwood]

I know about both of those user-specified limits. They are documented, as is 
the change in counting clauses in 9.0.

I’ll ask again, is there a hard upper limit on the value of maxBooleanClauses?

wunder

> On Apr 17, 2024, at 2:33 PM, Chris Hostetter  wrote:
> 
> 
> 
> : Is there a hard upper limit for maxBooleanClauses? We have someone hitting 
> a limit at 64k clauses after upgrading to 9.x.
> 
> There are two limits, one per-collection in solrconfig.xml that applies 
> to query parsing, and one global in solr.xml that applies to every query 
> including query expansion that hapens during query rewrite -- but those 
> have both existed since at least 8.1
> 
> What did change in 9.0 is that the global limit now enforced recursively 
> (by Lucene's index searcher) ...
> 
> https://solr.apache.org/guide/solr/latest/upgrade-notes/major-changes-in-solr-9.html#querying-and-indexing-2
> https://solr.apache.org/guide/solr/latest/configuration-guide/configuring-solr-xml.html#global-maxbooleanclauses
> https://solr.apache.org/guide/solr/latest/configuration-guide/caches-warming.html#maxbooleanclauses-element
> 
> 
> 
> -Hoss
> http://www.lucidworks.com/

Re: Invalid JSON on solr9 when using a binary field

[Karl Stoney]

Hi Thomas,
That link doesn’t seem to work for me (might be that my corporate AV is messing 
with it as it rewrites it to some outlook safe link!) – do you have an issue 
ref?

We’re trying to go to 9.5.0, which is the latest.

From: Thomas Corthals 
Date: Wednesday, 17 April 2024 at 16:49
To: users@solr.apache.org 
Cc: Michael Eves , Craig Wrigglesworth 

Subject: Re: Invalid JSON on solr9 when using a binary field
Hi Karl,

What is the exact version of Solr 9 you're trying to upgrade to?

This sounds very similar to this issue:
https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Flist%3Fusers%40solr.apache.org%3Agte%3D0d%3A%26header_subject%3DInvalid%2520JSON%2520response%2520with%2520UUID%2520field&data=05%7C02%7CKarl.Stoney%40autotrader.co.uk%7Cd4aa4ec734fa44913fc508dc5ef6004f%7C926f3743f3d24b8a816818cfcbe776fe%7C0%7C0%7C638489657913634950%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=7VmK3hGPAZLiGk90tj5SHGzGVc62i56rkTNidVjXmVM%3D&reserved=0

Thomas

Op wo 17 apr 2024 om 16:55 schreef Karl Stoney
:

> Hi,
> I’m currently looking into the solr 8 -> solr 9 upgrade, and we’ve noticed
> that if a document is using a binary field, the json returned is invalid
> because the value is not quoted:
>
> For example on solr 8 we’d see:
>
> ```
> "STOCK_ITEM_BINARY_FIELD":”OikKAfqEdXJzSWRjNTEwMj…”
> ```
>
> But on solr 8 we get back:
>
> ```
> "STOCK_ITEM_BINARY_FIELD":OikKAfqEdXJzSWRjNTEwMj…
> ```
>
> (note both these examples are observed through the Solr UI too):
>
> This feels like a bug, but wanted to check here before I raised it as one?
>
>
> Unless expressly stated otherwise in this email, this e-mail is sent on
> behalf of Auto Trader Limited Registered Office: 1 Tony Wilson Place,
> Manchester, Lancashire, M15 4FN (Registered in England No. 03909628). Auto
> Trader Limited is part of the Auto Trader Group Plc group. This email and
> any files transmitted with it are confidential and may be legally
> privileged, and intended solely for the use of the individual or entity to
> whom they are addressed. If you have received this email in error please
> notify the sender. This email message has been swept for the presence of
> computer viruses.
>


Unless expressly stated otherwise in this email, this e-mail is sent on behalf 
of Auto Trader Limited Registered Office: 1 Tony Wilson Place, Manchester, 
Lancashire, M15 4FN (Registered in England No. 03909628). Auto Trader Limited 
is part of the Auto Trader Group Plc group. This email and any files 
transmitted with it are confidential and may be legally privileged, and 
intended solely for the use of the individual or entity to whom they are 
addressed. If you have received this email in error please notify the sender. 
This email message has been swept for the presence of computer viruses.