[jira] [Commented] (SOLR-12833) Use timed-out lock in DistributedUpdateProcessor

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (SOLR-12833) Use timed-out lock in DistributedUpdateProcessor

JIRA jira@apache.org

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

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

Commit e5329f27c036b1017feb15651aca6dd374584308 in lucene-solr's branch refs/heads/branch_7x from markrmiller
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=e5329f2 ]

SOLR-12833: Add configurable timeout to VersionBucket lock.


> Use timed-out lock in DistributedUpdateProcessor
> ------------------------------------------------
>
>                 Key: SOLR-12833
>                 URL: https://issues.apache.org/jira/browse/SOLR-12833
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public)
>          Components: update, UpdateRequestProcessors
>    Affects Versions: 7.5, master (8.0)
>            Reporter: jefferyyuan
>            Assignee: Mark Miller
>            Priority: Minor
>             Fix For: master (8.0)
>
>         Attachments: SOLR-12833.patch, SOLR-12833.patch
>
>
> There is a synchronize block that blocks other update requests whose IDs fall in the same hash bucket. The update waits forever until it gets the lock at the synchronize block, this can be a problem in some cases.
>  
> Some add/update requests (for example updates with spatial/shape analysis) like may take time (30+ seconds or even more), this would the request time out and fail.
> Client may retry the same requests multiple times or several minutes, this would make things worse.
> The server side receives all the update requests but all except one can do nothing, have to wait there. This wastes precious memory and cpu resource.
> We have seen the case 2000+ threads are blocking at the synchronize lock, and only a few updates are making progress. Each thread takes 3+ mb memory which causes OOM.
> Also if the update can't get the lock in expected time range, its better to fail fast.
>  
> We can have one configuration in solrconfig.xml: updateHandler/versionLock/timeInMill, so users can specify how long they want to wait the version bucket lock.
> The default value can be -1, so it behaves same - wait forever until it gets the lock.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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