[jira] [Updated] (SOLR-17237) JSON Writer appears to return invalid JSON when binary fields are used
[ https://issues.apache.org/jira/browse/SOLR-17237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Stoney updated SOLR-17237: --- Attachment: Screenshot 2024-04-29 at 08.54.30.png > JSON Writer appears to return invalid JSON when binary fields are used > -- > > Key: SOLR-17237 > URL: https://issues.apache.org/jira/browse/SOLR-17237 > Project: Solr > Issue Type: Bug > Components: JSON Request API >Affects Versions: 9.5.0 >Reporter: Karl Stoney >Priority: Major > Labels: json > Attachments: Screenshot 2024-04-18 at 09.16.23.png, Screenshot > 2024-04-29 at 08.54.30.png > > > Hello, > As per the thread on the user group, we're currently looking at upgrading to > solr 9.5.0, from v8. > We have built a fresh solr 9.5.0 from scratch, and have observed that when > requesting application/json, binary fields are not quoted - thus resulting in > invalid JSON. > I found https://issues.apache.org/jira/browse/SOLR-10653, which looks very > similar, and was "fixed" in 9.5.0. > Here's an example (partial) response that you can see (truncated the actual > value though): > ``` > "PARTNER_SITES_ADVERT_STATUS":"EXPIRED", > "DATE_OF_REGISTRATION_EPOCH":1584403200, > "STOCK_ITEM_BINARY_FIELD":OikKAfqLb3JpZ2luU291cmNlQ0=, > "FUEL_CAPACITY_VALUE":59.0 > ``` -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
[jira] [Commented] (SOLR-17237) JSON Writer appears to return invalid JSON when binary fields are used
[ https://issues.apache.org/jira/browse/SOLR-17237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17841887#comment-17841887 ] Karl Stoney commented on SOLR-17237: Hello! Sorry for the delay in getting back to you, I was away last week. Whilst I was off - someone at work debugged it: Problem's here in 9.5.0 release https://github.com/apache/solr/blob/cdd27dd15c3a6574032e9b1b92b148ab4e383599/solr/core/src/java/org/apache/solr/schema/BinaryField.java#L61 BinaryField tells the response writer the field doesn't need escaping, then the Jackson writer it's picked uses that to write the raw value https://github.com/apache/solr/blob/cdd27dd15c3a6574032e9b1b92b148ab4e383599/solr/core/src/java/org/apache/solr/response/JacksonJsonWriter.java#L131 I was going to submit a PR as it's just a case of ignoring the fields hint, then realised someone already fixed it last month for their UUID type problem, which also fixes binary https://issues.apache.org/jira/browse/SOLR-17110 https://github.com/apache/solr/blob/main/solr/core/src/java/org/apache/solr/response/JacksonJsonWriter.java#L131 I bumped our cluster to 9.6.0 this morning and can confirm the binary field is now quoted: !Screenshot 2024-04-29 at 08.54.30.png! > JSON Writer appears to return invalid JSON when binary fields are used > -- > > Key: SOLR-17237 > URL: https://issues.apache.org/jira/browse/SOLR-17237 > Project: Solr > Issue Type: Bug > Components: JSON Request API >Affects Versions: 9.5.0 >Reporter: Karl Stoney >Priority: Major > Labels: json > Attachments: Screenshot 2024-04-18 at 09.16.23.png, Screenshot > 2024-04-29 at 08.54.30.png > > > Hello, > As per the thread on the user group, we're currently looking at upgrading to > solr 9.5.0, from v8. > We have built a fresh solr 9.5.0 from scratch, and have observed that when > requesting application/json, binary fields are not quoted - thus resulting in > invalid JSON. > I found https://issues.apache.org/jira/browse/SOLR-10653, which looks very > similar, and was "fixed" in 9.5.0. > Here's an example (partial) response that you can see (truncated the actual > value though): > ``` > "PARTNER_SITES_ADVERT_STATUS":"EXPIRED", > "DATE_OF_REGISTRATION_EPOCH":1584403200, > "STOCK_ITEM_BINARY_FIELD":OikKAfqLb3JpZ2luU291cmNlQ0=, > "FUEL_CAPACITY_VALUE":59.0 > ``` -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
[jira] [Created] (SOLR-17237) JSON Writer appears to return invalid JSON when binary fields are used
Karl Stoney created SOLR-17237: -- Summary: JSON Writer appears to return invalid JSON when binary fields are used Key: SOLR-17237 URL: https://issues.apache.org/jira/browse/SOLR-17237 Project: Solr Issue Type: Bug Security Level: Public (Default Security Level. Issues are Public) Components: JSON Request API Affects Versions: 9.5.0 Reporter: Karl Stoney Attachments: Screenshot 2024-04-18 at 09.16.23.png Hello, As per the thread on the user group, we're currently looking at upgrading to solr 9.5.0, from v8. We have built a fresh solr 9.5.0 from scratch, and have observed that when requesting application/json, binary fields are not quoted - thus resulting in invalid JSON. I found https://issues.apache.org/jira/browse/SOLR-10653, which looks very similar, and was "fixed" in 9.5.0. Here's an example (partial) response that you can see (truncated the actual value though): ``` "PARTNER_SITES_ADVERT_STATUS":"EXPIRED", "DATE_OF_REGISTRATION_EPOCH":1584403200, "STOCK_ITEM_BINARY_FIELD":OikKAfqLb3JpZ2luU291cmNlQ0=, "FUEL_CAPACITY_VALUE":59.0 ``` -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
[jira] [Created] (SOLR-15804) Unable to view XML files via the Solr Collection GUI
Karl Stoney created SOLR-15804:
--
Summary: Unable to view XML files via the Solr Collection GUI
Key: SOLR-15804
URL: https://issues.apache.org/jira/browse/SOLR-15804
Project: Solr
Issue Type: Bug
Security Level: Public (Default Security Level. Issues are Public)
Components: Admin UI
Affects Versions: 8.11
Reporter: Karl Stoney
Hi,
Updated our cluster to 8.11.0 in testing this morning and noticed that the
“file” explorer is broken when viewing a file.
To recreate:
* Select a collection
* Select files
* Click on an XML file
{code:java}
13:55:58.753 [qtp33233312-2347] ERROR
org.apache.solr.handler.RequestHandlerBase -
org.apache.solr.common.SolrException: Requested content type
'text/xml;charset=utf-8' is not supported.
org.apache.solr.common.SolrException: Requested content type
'text/xml;charset=utf-8' is not supported.
at
org.apache.solr.handler.admin.ShowFileRequestHandler.getSafeContentType(ShowFileRequestHandler.java:269)
~[solr-core-8.11.0.jar:8.11.0 e912fdd5b632267a9088507a2a6bcbc75108f381 -
jpountz - 2021-11-09 14:08:51]
at
org.apache.solr.handler.admin.ShowFileRequestHandler.showFromZooKeeper(ShowFileRequestHandler.java:186)
~[solr-core-8.11.0.jar:8.11.0 e912fdd5b632267a9088507a2a6bcbc75108f381 -
jpountz - 2021-11-09 14:08:51]
at
org.apache.solr.handler.admin.ShowFileRequestHandler.handleRequestBody(ShowFileRequestHandler.java:137)
~[solr-core-8.11.0.jar:8.11.0 e912fdd5b632267a9088507a2a6bcbc75108f381 -
jpountz - 2021-11-09 14:08:51]
at
org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:216)
~[solr-core-8.11.0.jar:8.11.0 e912fdd5b632267a9088507a2a6bcbc75108f381 -
jpountz - 2021-11-09 14:08:51]
at org.apache.solr.core.SolrCore.execute(SolrCore.java:2637)
~[solr-core-8.11.0.jar:8.11.0 e912fdd5b632267a9088507a2a6bcbc75108f381 -
jpountz - 2021-11-09 14:08:51]
at org.apache.solr.servlet.HttpSolrCall.execute(HttpSolrCall.java:794)
~[solr-core-8.11.0.jar:8.11.0 e912fdd5b632267a9088507a2a6bcbc75108f381 -
jpountz - 2021-11-09 14:08:51]
at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:567)
~[solr-core-8.11.0.jar:8.11.0 e912fdd5b632267a9088507a2a6bcbc75108f381 -
jpountz - 2021-11-09 14:08:51]
at
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:427)
~[solr-core-8.11.0.jar:8.11.0 e912fdd5b632267a9088507a2a6bcbc75108f381 -
jpountz - 2021-11-09 14:08:51]
at
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:357)
~[solr-core-8.11.0.jar:8.11.0 e912fdd5b632267a9088507a2a6bcbc75108f381 -
jpountz - 2021-11-09 14:08:51]
at
org.eclipse.jetty.servlet.FilterHolder.doFilter(FilterHolder.java:201)
~[jetty-servlet-9.4.44.v20210927.jar:9.4.44.v20210927]
at
org.eclipse.jetty.servlet.ServletHandler$Chain.doFilter(ServletHandler.java:1601)
~[jetty-servlet-9.4.44.v20210927.jar:9.4.44.v20210927]
at
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:548)
~[jetty-servlet-9.4.44.v20210927.jar:9.4.44.v20210927]
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
~[jetty-server-9.4.44.v20210927.jar:9.4.44.v20210927]
at
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:600)
~[jetty-security-9.4.44.v20210927.jar:9.4.44.v20210927]
at
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127)
~[jetty-server-9.4.44.v20210927.jar:9.4.44.v20210927]
at
org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:235)
~[jetty-server-9.4.44.v20210927.jar:9.4.44.v20210927]
at
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1624)
~[jetty-server-9.4.44.v20210927.jar:9.4.44.v20210927]
at
org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:233)
~[jetty-server-9.4.44.v20210927.jar:9.4.44.v20210927]
at
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1434)
~[jetty-server-9.4.44.v20210927.jar:9.4.44.v20210927]
at
org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:188)
~[jetty-server-9.4.44.v20210927.jar:9.4.44.v20210927]
at
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:501)
~[jetty-servlet-9.4.44.v20210927.jar:9.4.44.v20210927]
at
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1594)
~[jetty-server-9.4.44.v20210927.jar:9.4.44.v20210927]
at
org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:186)
~[jetty-server-9.4.44.v20210927.jar:9.4.44.v20210927]
at
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1349)
~[jetty-server-9.4.44.v20210927.jar:9.4.44.v20210927]
[jira] [Commented] (SOLR-15311) MODIFYCOLLECTION configName with async fails
[
https://issues.apache.org/jira/browse/SOLR-15311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17320175#comment-17320175
]
Karl Stoney commented on SOLR-15311:
Hey [~cpoerschke] - thanks for looking at it.
That's correct, the operation completes just fine - so it isn't a major issue.
I'm not sure about the thinking out loud part, from a naive end user
perspective, i'd like it to just work like the rest of the collections api in
that i send a RELOADCOLLECTION with an asyncid, and i can status that until the
whole operation is done.
> MODIFYCOLLECTION configName with async fails
>
>
> Key: SOLR-15311
> URL: https://issues.apache.org/jira/browse/SOLR-15311
> Project: Solr
> Issue Type: Bug
>Affects Versions: 8.8, 8.8.1
>Reporter: Karl Stoney
>Priority: Minor
>
> Hi,
> If you perform a `MODIFYCOLLECTION` with an `async` number, it will fail
> after about 30 seconds. However the exact same request without async works
> just fine and returns successfully instantly.
> {{
> 11:34:01.057
> [OverseerThreadFactory-20-thread-5-processing-n:solr-0.search-solr.svc.cluster.local:80_solr]
> ERROR org.apache.solr.cloud.api.collections.OverseerCollectionMessageHandler
> - Collection: at-uk-004 operation: modifycollection
> failed:org.apache.solr.common.SolrException: Could not modify collection {
> "collection":"at-uk-004",
> "async":"1617449610",
> "operation":"modifycollection"}
> at
> org.apache.solr.cloud.api.collections.OverseerCollectionMessageHandler.modifyCollection(OverseerCollectionMessageHandler.java:669)
> at
> org.apache.solr.cloud.api.collections.OverseerCollectionMessageHandler.processMessage(OverseerCollectionMessageHandler.java:266)
> at
> org.apache.solr.cloud.OverseerTaskProcessor$Runner.run(OverseerTaskProcessor.java:524)
> at
> org.apache.solr.common.util.ExecutorUtil$MDCAwareThreadPoolExecutor.lambda$execute$0(ExecutorUtil.java:218)
> 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)
> }}
> The request i'm sending (POST):
> {{
> const url = `${this.host}/solr/admin/collections`
> const searchParams = {
> action: 'MODIFYCOLLECTION',
> collection: collectionName,
> 'collection.configName': newConfigName
> }
> }}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
[jira] [Created] (SOLR-15311) MODIFYCOLLECTION configName with async fails
Karl Stoney created SOLR-15311:
--
Summary: MODIFYCOLLECTION configName with async fails
Key: SOLR-15311
URL: https://issues.apache.org/jira/browse/SOLR-15311
Project: Solr
Issue Type: Bug
Security Level: Public (Default Security Level. Issues are Public)
Affects Versions: 8.8.1, 8.8
Reporter: Karl Stoney
Hi,
If you perform a `MODIFYCOLLECTION` with an `async` number, it will fail after
about 30 seconds. However the exact same request without async works just fine
and returns successfully instantly.
{{
11:34:01.057
[OverseerThreadFactory-20-thread-5-processing-n:solr-0.search-solr.svc.cluster.local:80_solr]
ERROR org.apache.solr.cloud.api.collections.OverseerCollectionMessageHandler -
Collection: at-uk-004 operation: modifycollection
failed:org.apache.solr.common.SolrException: Could not modify collection {
"collection":"at-uk-004",
"async":"1617449610",
"operation":"modifycollection"}
at
org.apache.solr.cloud.api.collections.OverseerCollectionMessageHandler.modifyCollection(OverseerCollectionMessageHandler.java:669)
at
org.apache.solr.cloud.api.collections.OverseerCollectionMessageHandler.processMessage(OverseerCollectionMessageHandler.java:266)
at
org.apache.solr.cloud.OverseerTaskProcessor$Runner.run(OverseerTaskProcessor.java:524)
at
org.apache.solr.common.util.ExecutorUtil$MDCAwareThreadPoolExecutor.lambda$execute$0(ExecutorUtil.java:218)
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)
}}
The request i'm sending (POST):
{{
const url = `${this.host}/solr/admin/collections`
const searchParams = {
action: 'MODIFYCOLLECTION',
collection: collectionName,
'collection.configName': newConfigName
}
}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
[jira] [Updated] (SOLR-15306) commit does not use async API
[ https://issues.apache.org/jira/browse/SOLR-15306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Stoney updated SOLR-15306: --- Description: It would be really useful if the commit api (particularly expungeDeletes due to the potentially long duration) supported the async api. On our medium sized (30gb) collection it takes around 5 minutes to run, so feels like a good candidate for async polling. was: It would be really useful if the commit api (particularly expungeDeletes due to the potentially log duration) supported the async api. On our medium sized (30gb) collection it takes around 5 minutes to run, so feels like a good candidate for async polling. > commit does not use async API > - > > Key: SOLR-15306 > URL: https://issues.apache.org/jira/browse/SOLR-15306 > Project: Solr > Issue Type: Wish > Security Level: Public(Default Security Level. Issues are Public) > Components: update >Affects Versions: 8.8, 8.8.1 >Reporter: Karl Stoney >Priority: Minor > > It would be really useful if the commit api (particularly expungeDeletes due > to the potentially long duration) supported the async api. > On our medium sized (30gb) collection it takes around 5 minutes to run, so > feels like a good candidate for async polling. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
[jira] [Comment Edited] (SOLR-15306) commit does not use async API
[
https://issues.apache.org/jira/browse/SOLR-15306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17313071#comment-17313071
]
Karl Stoney edited comment on SOLR-15306 at 4/1/21, 10:31 AM:
--
FWIW we also get these in the logs when it goes over 60s due to it (presumably)
hitting a jetty timeout
{{
10:14:18.055
[updateExecutor-9-thread-777-processing-n:solr-0.search-solr.svc.cluster.local:80_solr
x:at-uk-002_shard1_replica_n4 c:at-uk-002 s:shard1 r:core_node6] ERROR
org.apache.solr.update.SolrCmdDistributor -
org.apache.solr.client.solrj.SolrServerException: Idle timeout expired:
60/60 ms
at
org.apache.solr.client.solrj.impl.Http2SolrClient.request(Http2SolrClient.java:430)
at
org.apache.solr.client.solrj.impl.Http2SolrClient.request(Http2SolrClient.java:761)
at
org.apache.solr.client.solrj.impl.ConcurrentUpdateHttp2SolrClient.request(ConcurrentUpdateHttp2SolrClient.java:370)
at org.apache.solr.client.solrj.SolrClient.request(SolrClient.java:1290)
at
org.apache.solr.update.SolrCmdDistributor.doRequest(SolrCmdDistributor.java:345)
at
org.apache.solr.update.SolrCmdDistributor.lambda$submit$0(SolrCmdDistributor.java:334)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at
com.codahale.metrics.InstrumentedExecutorService$InstrumentedRunnable.run(InstrumentedExecutorService.java:180)
at
org.apache.solr.common.util.ExecutorUtil$MDCAwareThreadPoolExecutor.lambda$execute$0(ExecutorUtil.java:218)
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)
Caused by: java.util.concurrent.TimeoutException: Idle timeout expired:
60/60 ms
at
org.eclipse.jetty.io.IdleTimeout.checkIdleTimeout(IdleTimeout.java:171)
at org.eclipse.jetty.io.IdleTimeout.idleCheck(IdleTimeout.java:113)
at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at
java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
... 3 more
}}
was (Author: kstoney):
FWIW we also get these in the logs when it goes over 60s:
{{
10:14:18.055
[updateExecutor-9-thread-777-processing-n:solr-0.search-solr.svc.cluster.local:80_solr
x:at-uk-002_shard1_replica_n4 c:at-uk-002 s:shard1 r:core_node6] ERROR
org.apache.solr.update.SolrCmdDistributor -
org.apache.solr.client.solrj.SolrServerException: Idle timeout expired:
60/60 ms
at
org.apache.solr.client.solrj.impl.Http2SolrClient.request(Http2SolrClient.java:430)
at
org.apache.solr.client.solrj.impl.Http2SolrClient.request(Http2SolrClient.java:761)
at
org.apache.solr.client.solrj.impl.ConcurrentUpdateHttp2SolrClient.request(ConcurrentUpdateHttp2SolrClient.java:370)
at org.apache.solr.client.solrj.SolrClient.request(SolrClient.java:1290)
at
org.apache.solr.update.SolrCmdDistributor.doRequest(SolrCmdDistributor.java:345)
at
org.apache.solr.update.SolrCmdDistributor.lambda$submit$0(SolrCmdDistributor.java:334)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at
com.codahale.metrics.InstrumentedExecutorService$InstrumentedRunnable.run(InstrumentedExecutorService.java:180)
at
org.apache.solr.common.util.ExecutorUtil$MDCAwareThreadPoolExecutor.lambda$execute$0(ExecutorUtil.java:218)
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)
Caused by: java.util.concurrent.TimeoutException: Idle timeout expired:
60/60 ms
at
org.eclipse.jetty.io.IdleTimeout.checkIdleTimeout(IdleTimeout.java:171)
at org.eclipse.jetty.io.IdleTimeout.idleCheck(IdleTimeout.java:113)
at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at
java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
... 3 more
}}
> commit does not use async
[jira] [Comment Edited] (SOLR-15306) commit does not use async API
[
https://issues.apache.org/jira/browse/SOLR-15306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17313071#comment-17313071
]
Karl Stoney edited comment on SOLR-15306 at 4/1/21, 10:27 AM:
--
FWIW we also get these in the logs when it goes over 60s:
{{
10:14:18.055
[updateExecutor-9-thread-777-processing-n:solr-0.search-solr.svc.cluster.local:80_solr
x:at-uk-002_shard1_replica_n4 c:at-uk-002 s:shard1 r:core_node6] ERROR
org.apache.solr.update.SolrCmdDistributor -
org.apache.solr.client.solrj.SolrServerException: Idle timeout expired:
60/60 ms
at
org.apache.solr.client.solrj.impl.Http2SolrClient.request(Http2SolrClient.java:430)
at
org.apache.solr.client.solrj.impl.Http2SolrClient.request(Http2SolrClient.java:761)
at
org.apache.solr.client.solrj.impl.ConcurrentUpdateHttp2SolrClient.request(ConcurrentUpdateHttp2SolrClient.java:370)
at org.apache.solr.client.solrj.SolrClient.request(SolrClient.java:1290)
at
org.apache.solr.update.SolrCmdDistributor.doRequest(SolrCmdDistributor.java:345)
at
org.apache.solr.update.SolrCmdDistributor.lambda$submit$0(SolrCmdDistributor.java:334)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at
com.codahale.metrics.InstrumentedExecutorService$InstrumentedRunnable.run(InstrumentedExecutorService.java:180)
at
org.apache.solr.common.util.ExecutorUtil$MDCAwareThreadPoolExecutor.lambda$execute$0(ExecutorUtil.java:218)
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)
Caused by: java.util.concurrent.TimeoutException: Idle timeout expired:
60/60 ms
at
org.eclipse.jetty.io.IdleTimeout.checkIdleTimeout(IdleTimeout.java:171)
at org.eclipse.jetty.io.IdleTimeout.idleCheck(IdleTimeout.java:113)
at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at
java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
... 3 more
}}
was (Author: kstoney):
FWIW we also get these in the logs when it goes over 60s:
{{10:14:18.055
[updateExecutor-9-thread-777-processing-n:solr-0.search-solr.svc.cluster.local:80_solr
x:at-uk-002_shard1_replica_n4 c:at-uk-002 s:shard1 r:core_node6] ERROR
org.apache.solr.update.SolrCmdDistributor -
org.apache.solr.client.solrj.SolrServerException: Idle timeout expired:
60/60 ms
at
org.apache.solr.client.solrj.impl.Http2SolrClient.request(Http2SolrClient.java:430)
at
org.apache.solr.client.solrj.impl.Http2SolrClient.request(Http2SolrClient.java:761)
at
org.apache.solr.client.solrj.impl.ConcurrentUpdateHttp2SolrClient.request(ConcurrentUpdateHttp2SolrClient.java:370)
at org.apache.solr.client.solrj.SolrClient.request(SolrClient.java:1290)
at
org.apache.solr.update.SolrCmdDistributor.doRequest(SolrCmdDistributor.java:345)
at
org.apache.solr.update.SolrCmdDistributor.lambda$submit$0(SolrCmdDistributor.java:334)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at
com.codahale.metrics.InstrumentedExecutorService$InstrumentedRunnable.run(InstrumentedExecutorService.java:180)
at
org.apache.solr.common.util.ExecutorUtil$MDCAwareThreadPoolExecutor.lambda$execute$0(ExecutorUtil.java:218)
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)
Caused by: java.util.concurrent.TimeoutException: Idle timeout expired:
60/60 ms
at
org.eclipse.jetty.io.IdleTimeout.checkIdleTimeout(IdleTimeout.java:171)
at org.eclipse.jetty.io.IdleTimeout.idleCheck(IdleTimeout.java:113)
at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at
java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
... 3 more
}}
> commit does not use async API
> -
>
>
[jira] [Commented] (SOLR-15306) commit does not use async API
[
https://issues.apache.org/jira/browse/SOLR-15306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17313071#comment-17313071
]
Karl Stoney commented on SOLR-15306:
FWIW we also get these in the logs when it goes over 60s:
{{10:14:18.055
[updateExecutor-9-thread-777-processing-n:solr-0.search-solr.svc.cluster.local:80_solr
x:at-uk-002_shard1_replica_n4 c:at-uk-002 s:shard1 r:core_node6] ERROR
org.apache.solr.update.SolrCmdDistributor -
org.apache.solr.client.solrj.SolrServerException: Idle timeout expired:
60/60 ms
at
org.apache.solr.client.solrj.impl.Http2SolrClient.request(Http2SolrClient.java:430)
at
org.apache.solr.client.solrj.impl.Http2SolrClient.request(Http2SolrClient.java:761)
at
org.apache.solr.client.solrj.impl.ConcurrentUpdateHttp2SolrClient.request(ConcurrentUpdateHttp2SolrClient.java:370)
at org.apache.solr.client.solrj.SolrClient.request(SolrClient.java:1290)
at
org.apache.solr.update.SolrCmdDistributor.doRequest(SolrCmdDistributor.java:345)
at
org.apache.solr.update.SolrCmdDistributor.lambda$submit$0(SolrCmdDistributor.java:334)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at
com.codahale.metrics.InstrumentedExecutorService$InstrumentedRunnable.run(InstrumentedExecutorService.java:180)
at
org.apache.solr.common.util.ExecutorUtil$MDCAwareThreadPoolExecutor.lambda$execute$0(ExecutorUtil.java:218)
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)
Caused by: java.util.concurrent.TimeoutException: Idle timeout expired:
60/60 ms
at
org.eclipse.jetty.io.IdleTimeout.checkIdleTimeout(IdleTimeout.java:171)
at org.eclipse.jetty.io.IdleTimeout.idleCheck(IdleTimeout.java:113)
at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at
java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
... 3 more
}}
> commit does not use async API
> -
>
> Key: SOLR-15306
> URL: https://issues.apache.org/jira/browse/SOLR-15306
> Project: Solr
> Issue Type: Wish
> Security Level: Public(Default Security Level. Issues are Public)
> Components: update
>Affects Versions: 8.8, 8.8.1
>Reporter: Karl Stoney
>Priority: Minor
>
> It would be really useful if the commit api (particularly expungeDeletes due
> to the potentially log duration) supported the async api.
> On our medium sized (30gb) collection it takes around 5 minutes to run, so
> feels like a good candidate for async polling.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
[jira] [Created] (SOLR-15306) commit does not use async API
Karl Stoney created SOLR-15306: -- Summary: commit does not use async API Key: SOLR-15306 URL: https://issues.apache.org/jira/browse/SOLR-15306 Project: Solr Issue Type: Wish Security Level: Public (Default Security Level. Issues are Public) Components: update Affects Versions: 8.8.1, 8.8 Reporter: Karl Stoney It would be really useful if the commit api (particularly expungeDeletes due to the potentially log duration) supported the async api. On our medium sized (30gb) collection it takes around 5 minutes to run, so feels like a good candidate for async polling. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
