lucene-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ishan Chattopadhyaya (Jira)" <>
Subject [jira] [Commented] (SOLR-13963) JavaBinCodec has concurrent modification of CharArr resulting in corrupt intranode updates
Date Tue, 26 Nov 2019 13:38:00 GMT


Ishan Chattopadhyaya commented on SOLR-13963:

I wouldn't be surprised if Noble found a new way of using git that even Torvalds didn't see
coming, let alone our humble asfbot. 😉

> JavaBinCodec has concurrent modification of CharArr resulting in corrupt intranode updates
> ------------------------------------------------------------------------------------------
>                 Key: SOLR-13963
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>    Affects Versions: 8.3
>            Reporter: Colvin Cowie
>            Assignee: Noble Paul
>            Priority: Blocker
>             Fix For: 8.3.1
>         Attachments:, SOLR-13963.patch, SOLR-13963.patch
> Discussed on the mailing list "Possible data corruption in JavaBinCodec in Solr 8.3 during
distributed update?"
> In summary, after moving to 8.3 we had a consistent (but non-deterministic) set of failing
tests where the data being sent in intranode requests was _sometimes_ corrupted. For example
if the well formed data was
>  _'fieldName':"this is a long string"_
>  The error we saw from Solr might be that
>  unknown field _+'fieldNamis a long string"+_ 
>  The change that indirectly caused to this issue to materialize was from SOLR-13682 which
meant that org.apache.solr.common.SolrInputDocument.writeMap(EntryWriter) would call org.apache.solr.common.SolrInputField.getValue()
rather than org.apache.solr.common.SolrInputField.getRawValue() as it had before.
>  getRawValue for a string calls org.apache.solr.common.util.ByteArrayUtf8CharSequence._getStr()
which in this context calls
>  org.apache.solr.common.util.JavaBinCodec.getStringProvider()
>  JavaBinCodec has a CharArr, _arr_, which is modified in two different locations, but
only one of which is protected with a synchronized block
>  getStringProvider() synchronizes on _arr_:
>  []
>  but  _readStr() doesn't:
>  []
>  The two methods are called concurrently, but wheren't prior to SOLR-13682.
>  Adding a synchronized block into _readStr() around the modification of _arr_ fixes
the problem as far as I can see.
> Also, the problem does not seem to occur when using the dynamic schema mode of autoCreateFields=true
in the updateRequestProcessorChain.

This message was sent by Atlassian Jira

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message