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 (#7).

Change subject: [WIP]log block manager:mark container as 'non-writable' after 
IOError
......................................................................

[WIP]log block manager:mark container as 'non-writable' after
IOError

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 patch marks container as 'non-writable' if there is IOError
during syncing data and metdata while closing a block, to avoid
further in-memory state inconsistency. It also adds test case
for fault injection around block closure to ensure consistent
container's in-memory accounting.

Change-Id: I15062b9d82c9cb563fb6bb2af7ec89da5f71e28f
---
M src/kudu/fs/block_manager-test.cc
M src/kudu/fs/log_block_manager.cc
M src/kudu/util/env_posix.cc
3 files changed, 114 insertions(+), 18 deletions(-)


  git pull ssh://gerrit.cloudera.org:29418/kudu refs/changes/74/7374/7
-- 
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: 7
Gerrit-Project: kudu
Gerrit-Branch: master
Gerrit-Owner: Hao Hao <[email protected]>
Gerrit-Reviewer: Andrew Wong <[email protected]>
Gerrit-Reviewer: Dan Burkert <[email protected]>
Gerrit-Reviewer: Hao Hao <[email protected]>
Gerrit-Reviewer: Kudu Jenkins
Gerrit-Reviewer: Tidy Bot

Reply via email to