Writing on different local-heap indexes will provoke LockObtainFailedException

Description

When we're using local-heap as directory type for our Lucene backend and we try to update different indexes, we will get a org.apache.lucene.store.LockObtainFailedException when we are writing on the second index.

The reason seems to be the fact that even if we define different `org.apache.lucene.store.Directory` instances for the different indexes, they share the same `org.apache.lucene.store.LockFactory` instance, which is `SingleInstanceLockFactory` and it do not support different locks.

The same test works well if the default directory type is used.

Environment

None

Assignee

Fabio Massimo Ercoli

Reporter

Fabio Massimo Ercoli

Labels

None

Suitable for new contributors

None

Feedback Requested

None

Components

Fix versions

Affects versions

Priority

Critical
Configure