Lucene error

Description

Got this error multiple times today. What might this be caused by?
I am using Zanata Platform 4.3.0.

Environment

None

Activity

Show:
Sean Flanigan
January 25, 2018, 1:07 AM

If you're sure there isn't another copy of Zanata running, it's probably a leftover .lock file from a crashed process.

So you should probably delete all the write.lock files under {{C:\Windows\System32\config\systemprofile\zanata\indexes}} and restart Zanata.

Oytun Tez
January 27, 2018, 2:07 PM

We are also encountering similar errors, in multiple workflows. , you may want to open a different ticket about this as you have been working on it.

The last similar error I have is this one (local Docker):

Sean Flanigan
January 29, 2018, 12:58 AM

It looks like I messed up the fix for ZNTA-1786, because I failed to actually set the locking strategy to native (as intended and even discussed with during the PR review).

I'll make a fix, but for now the workaround is just to delete all the .lock files before starting Zanata.

Oytun Tez
January 29, 2018, 4:50 AM

, what would be your suggestion for a clustered environment?

Sean Flanigan
January 29, 2018, 5:00 AM

You need (or try the Elastic Search back-end with a newer version of Hibernate Search - this might require a Hibernate upgrade too)

Ready for Release

Assignee

Unassigned

Reporter

B L

Labels

None

Tested Version/s

None

Fix versions

Affects versions

Priority

unspecified
Configure