|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
Hi Brett,
I'm aware of that but the problem is that it only happens in production under load and is quite erratic. It also only happens if the batch loading is enabled - it goes away if we disable it (but that might be unrelated to batch loading, just that things are faster). We weren't able to reproduce it in development.
If it might help a bit, it's a regression from 4.1.7 to 4.1.8. We run with 4.1.7 for a while without any problem.
I'll see if we can find the commit which introduces the regression next week by bissecting between 4.1.7 and 4.1.8 and pushing snapshots to our servers.
Sorry we're not very helpful with this one...