[
https://issues.apache.org/jira/browse/SOLR-17086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17798601#comment-17798601
]
Hakan Özler commented on SOLR-17086:
------------------------------------
Hey [~gerlowskija] ! Sorry for being late in responding your question. I took
the following steps to reproduce the problem:
* Set up a SolrCloud cluster with two solr instances in K8s.
* Created a collection 'myCollection' with rf=1 and shard=1 on the Admin UI
using the '_default' configset.
* Ran the following cURL command to add a new replica to the one-shard
'myCollection' collection:
*
{code:java}
curl -i -L -X POST \
-H "Content-Type:application/json" \
-H "Authorization:Basic ...=" \
-d \
'{"type":"NRT", "async": "11"}' \
'https://solr.host/api/collections/myCollection/shards/shard1/replicas' {code}
* Afterwards, The curl returns with 500. There were two error messages in the
stack trace, I'm sharing with you: error1.json and error2.json.
I hope this can help you to reproduce the same situation. I've also attached
the response of the ADDREPLICA request.
> v2 Backup and Replica creation: HTTP 500 error messages
> -------------------------------------------------------
>
> Key: SOLR-17086
> URL: https://issues.apache.org/jira/browse/SOLR-17086
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Backup/Restore, v2 API
> Affects Versions: 9.4
> Reporter: Hakan Özler
> Assignee: Jason Gerlowski
> Priority: Major
> Attachments: addreplica-result.json, error1.json, error2.json
>
>
> I've encountered two problems related to the v2 API in 9.4.
>
> 1. Creating a backup [1] request using the v2 api directives sporadically
> returns `An exception was not mapped due to exception mapper failure. The
> HTTP 500 response will be returned` with the following stack trace. However,
> the backup process is always successfully completed. Here is an example
> backup request to produce this problem:
> {code:java}
> curl -i -L -X POST \
> -H "Content-Type:application/json" \
> -d \
> '{
> "repository": "s3",
> "location": "level-1-folder/level-2-folder/",
> "async": "1",
> }' \
>
> 'https://solr.host/api/collections/collection-name/backups/folder-name/versions'
> {code}
> Error trace:
> {code:java}
> java.lang.NullPointerException: Cannot invoke
> "org.apache.solr.request.SolrQueryRequest.getParams()" because
> "solrQueryRequest" is null
> at
> org.apache.solr.handler.api.V2ApiUtils.getMediaTypeFromWtParam(V2ApiUtils.java:92)
> at
> org.apache.solr.jersey.MediaTypeOverridingFilter.filter(MediaTypeOverridingFilter.java:64)
> at
> org.glassfish.jersey.server.ContainerFilteringStage$ResponseFilterStage.apply(ContainerFilteringStage.java:172)
> at
> org.glassfish.jersey.server.ContainerFilteringStage$ResponseFilterStage.apply(ContainerFilteringStage.java:139)
> at org.glassfish.jersey.process.internal.Stages.process(Stages.java:147)
> at
> org.glassfish.jersey.server.ServerRuntime$Responder.processResponse(ServerRuntime.java:378)
> {code}
>
> 2. Creating a replica [2] obviously has the same behavior. We're able to
> create a replica but we receive the message above at times. A snippet of an
> ADDREPLICA request:
>
> {code:java}
> curl -i -L -X POST \
> -H "Content-Type:application/json" \
> -d \
> '{"type":"NRT", "async": "1"}' \
> 'https://solr.host/api/collections/demo/shards/shard1/replicas' {code}
>
> 1.
> [https://solr.apache.org/guide/solr/latest/deployment-guide/collection-management.html#backup]
> 2.
> [https://solr.apache.org/guide/solr/latest/deployment-guide/replica-management.html#addreplica]
--
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
