[ 
https://issues.apache.org/jira/browse/SOLR-17231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18097635#comment-18097635
 ] 

ASF subversion and git services commented on SOLR-17231:
--------------------------------------------------------

Commit aa4d77520bf31eb34de86c7e7235a2ef1ff0bb60 in solr's branch 
refs/heads/branch_10x from Andrzej Bialecki
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=aa4d77520bf ]

SOLR-17231: Don't try buffering updates when there's no update log. (#3880)

(cherry picked from commit 1344194099c29ff2391266c77682198a3c6f4468)


> SolrCore.bufferUpdatesIfConstructing fails on PULL replicas
> -----------------------------------------------------------
>
>                 Key: SOLR-17231
>                 URL: https://issues.apache.org/jira/browse/SOLR-17231
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Chris M. Hostetter
>            Assignee: Andrzej Bialecki
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 10.0, 9.10.1
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> If a "Slice" is in the {{CONSTRUCTION}} state, then SolrCore initialization 
> for replicas of that Slice try to setup update buffering of the {{UpdateLog}} 
> – but this makes no sense for {{PULL}} replicas which have no update logs, 
> and causes a NPE....
> {code:java}
>   private void bufferUpdatesIfConstructing(CoreDescriptor coreDescriptor) {
> ...
>       if (slice.getState() == Slice.State.CONSTRUCTION) {
>         // set update log to buffer before publishing the core
>         getUpdateHandler().getUpdateLog().bufferUpdates();
>       }
>     }
> {code}
> I believe the fix is just for {{bufferUpdatesIfConstructing}} to check the 
> replica type? (or do a null check on {{getUpdateLog()}} ?)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to