lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shad Storhaug (Jira)" <j...@apache.org>
Subject [jira] [Resolved] (LUCENENET-617) Deadlock caused by NativeFSLockFactory
Date Sun, 29 Dec 2019 07:58:00 GMT

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

Shad Storhaug resolved LUCENENET-617.
-------------------------------------
    Resolution: Fixed

This has now been resolved in Lucene.NET 4.8.0-beta00007

> Deadlock caused by NativeFSLockFactory
> --------------------------------------
>
>                 Key: LUCENENET-617
>                 URL: https://issues.apache.org/jira/browse/LUCENENET-617
>             Project: Lucene.Net
>          Issue Type: Bug
>          Components: Lucene.Net Core
>    Affects Versions: Lucene.Net 4.8.0
>            Reporter: Shad Storhaug
>            Assignee: Shad Storhaug
>            Priority: Major
>             Fix For: Lucene.Net 4.8.0
>
>
> The NativeFSLockFactory is causing the {{Lucene.Net.Replicator.IndexAndTaxonomyReplicationClientTest::TestConsistencyOnExceptions()}}
test to deadlock on .NET Framework 4.5.1.
> It is also seemingly causing random failures to:
>  * {{Lucene.Net.Store.TestMockDirectoryWrapper::TestDiskFull()}}
> I have confirmed over 15 test runs that reverting the changes from the following commits
eliminates the issue without producing any side effects:
>  * [7f6c78570d4b7e5e4bbb8708acfe3a397822baca|https://github.com/apache/lucenenet/commit/7f6c78570d4b7e5e4bbb8708acfe3a397822baca]
>  * [c3e7ae30de1f23ec4198c817073096e302fc7a1b|https://github.com/apache/lucenenet/commit/c3e7ae30de1f23ec4198c817073096e302fc7a1b]
>  * [7f2b76a0a81c3fbe7dd5e329cbf1d6504dba9e2c|https://github.com/apache/lucenenet/commit/7f2b76a0a81c3fbe7dd5e329cbf1d6504dba9e2c]
> These include commits were introduced in [pull request #222|#222]([https://github.com/apache/lucenenet/pull/222])
and patches applied to it.
> It is unknown what the impact to consumers of 4.8.0-beta00006 is, but this issue appears
to be very rare judging by the tests.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message