[
https://issues.apache.org/jira/browse/LUCENE-6790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-6790:
---------------------------------------
Attachment: LUCENE-6790.patch
Patch, adding back the {{sync(commitLock)}} ... seems to fix the failure!
> Rollback (during tragic exception) should wait for concurrent commit to finish
> ------------------------------------------------------------------------------
>
> Key: LUCENE-6790
> URL: https://issues.apache.org/jira/browse/LUCENE-6790
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Fix For: Trunk, 5.4
>
> Attachments: LUCENE-6790.patch
>
>
> Causes this test failure:
> http://build-eu-00.elastic.co/job/lucene_linux_java8_64_test_only/63025/
> This is a regression, caused by LUCENE-6579 ... I remember hitting deadlock
> on that issue ... I'll try to add back acquiring the commitLock before
> rollback ...
> The issue happens if one thread is committing while another thread is
> handling a tragedy...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
