Hello Kudu Jenkins, I'd like you to reexamine a change. Please visit
http://gerrit.cloudera.org:8080/7374 to look at the new patch set (#4). Change subject: [WIP]log block manager:update container in-memory accounting after data is synced ...................................................................... [WIP]log block manager:update container in-memory accounting after data is synced Currently, container in-memory accounting is updated only after metadata get successfully synced. This may bring in inconsistent state between data and metadata when metadata record is actually been written to disk but fsync() does not succeed. This patche updates container's next_block_offset after data is being successfully fsync()ed. It also adds test case for fault injection around block closure to ensure correct container's in-memory accounting. Change-Id: I15062b9d82c9cb563fb6bb2af7ec89da5f71e28f --- M src/kudu/fs/block_manager-test.cc M src/kudu/fs/log_block_manager.cc 2 files changed, 119 insertions(+), 19 deletions(-) git pull ssh://gerrit.cloudera.org:29418/kudu refs/changes/74/7374/4 -- To view, visit http://gerrit.cloudera.org:8080/7374 To unsubscribe, visit http://gerrit.cloudera.org:8080/settings Gerrit-MessageType: newpatchset Gerrit-Change-Id: I15062b9d82c9cb563fb6bb2af7ec89da5f71e28f Gerrit-PatchSet: 4 Gerrit-Project: kudu Gerrit-Branch: master Gerrit-Owner: Hao Hao <hao....@cloudera.com> Gerrit-Reviewer: Kudu Jenkins Gerrit-Reviewer: Tidy Bot