lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Varun Thacker (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (SOLR-8412) SchemaManager should synchronize on performOperations method
Date Mon, 08 Feb 2016 20:06:40 GMT

     [ https://issues.apache.org/jira/browse/SOLR-8412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Varun Thacker resolved SOLR-8412.
---------------------------------
    Resolution: Not A Problem
      Assignee: Varun Thacker

Thanks Noble for confirming. Closing this Jira out. 

However I'll create a follow up Jira for the timeout bug in SchemaManager that I found while
working on this patch

> SchemaManager should synchronize on performOperations method
> ------------------------------------------------------------
>
>                 Key: SOLR-8412
>                 URL: https://issues.apache.org/jira/browse/SOLR-8412
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Varun Thacker
>            Assignee: Varun Thacker
>            Priority: Minor
>         Attachments: SOLR-8412.patch, SOLR-8412.patch, SOLR-8412.patch
>
>
> Currently SchemaManager synchronizes on {{schema.getSchemaUpdateLock()}} . We should
synzhronize on {{performOperations}} instead. 
> The net affect will be the same but the code will be more clear. {{schema.getSchemaUpdateLock()}}
is used when you want to edit a schema and add one field at a time. But the way SchemaManager
works is that it does bulk operations i.e performs all operations and then persists the final
schema . If there were two concurrent operations that took place, the later operation will
retry by fetching the latest schema .



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message