Backport file server serialization fix
Closed this issue · 1 comments
Sparrow noticed that some customers with very high merge activity are affected by extremely high latencies due to the file server serialization issue fixed for 2.0 in #85 and #118. For example, in ZD ticket 7618. When this occurs, nodes need a restart. For customers for which this is not an acceptable workaround and are schedule sensitiv, we may need to backport this fix. This is a ping to @evanmcc, @jonmeredith and @michellep to chime in on that, as I believe some are discussing another 1.4.9/1.5 release.
@engelsanchez i was misinformed earlier as the fix for this issue is present in more recent versions of 1.4.x. Looked at the commit log and we should be fine by updating the customer in question. My apoligies, closing.