Hi, On Wed, Jan 15, 2014 at 9:30 AM, Michael Dürig <mdue...@apache.org> wrote: > On 15.1.14 2:44 , Jukka Zitting wrote: >> It looks like the root cause of the failure is in the locking >> implementation and was just triggered by r1558270, so I'll mark it as >> a known issue for now and follow up in OAK-150. > > I don't think this is a locking problem since it only occurs with the > SegmentMK. > The test fails since Node.getStatus() returns EXISTING for a modified node > [1]. Not sure why the returned status is still wrong after Jukka's recent > fix though.
Hmm, you're right. The lock manager re-resolves the path to the node, and receives a node instance that no longer shows up as modified. Investigating... BR, Jukka Zitting
