[ https://issues.apache.org/jira/browse/SOLR-11182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Varun Thacker updated SOLR-11182: --------------------------------- Attachment: SOLR-11182.patch Thanks Shalin for pointing it out! I guess all we need is to throw it so that SplitOp will catch it , log it and throw a RuntimeException > Solr doesn't log IOException if a shard split fails > --------------------------------------------------- > > Key: SOLR-11182 > URL: https://issues.apache.org/jira/browse/SOLR-11182 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Reporter: Varun Thacker > Assignee: Varun Thacker > Attachments: SOLR-11182.patch > > > During a split shard operation the last message I see in the Solr logs was > this > {code} > date time INFO (parallelCoreAdminExecutor... SPLIT) [ ] > o.a.s.u.SolrIndexWriter Calling setCommitData with > IW:org.apache.solr.update.SolrIndexWriter@hex > {code} > But the split never completed according the the request status API. > {code} > ... > "Operation splitshard caused exception:": > "org.apache.solr.common.SolrException:org.apache.solr.common.SolrException", > "exception": { > "msg": null, > "rspCode": 500 > } > {code} > {{SolrIndexSplitter#split}} throws an IOException and in > DirectUpdateHandler2#split we catch it but never log an exception. We should > log the error and also throw it ? -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org