diff options
author | Pranith Kumar K <pkarampu@redhat.com> | 2013-04-03 15:27:01 +0530 |
---|---|---|
committer | Anand Avati <avati@redhat.com> | 2013-04-03 17:33:15 -0700 |
commit | 63119434365ddcea2d0b80aad0757e2201001af3 (patch) | |
tree | b51ffeffa5b85ca8e3ae45d9d7b9a1d012f43f72 /api | |
parent | 125e0cc4eb7042f5b8549c0b77140528c0fc1151 (diff) |
pump: Set self-heal readdir size in pump
Problem:
In Pump entry self-heal happens for each directory during the
first opendir using conservative merge. But in entry-self-heal
readdir is issued with '0' size. So entry self-heal is not
creating any files. After pump thinks entry self-heal is complete
it proceeds to heal each of the file in the directory it just
healed. Fortunately most of the times it chooses source-brick
in pump as read-child for readdir. This happens because readchild is the
subvolume on which lookup succeeds first. In pump lookup succeeds
faster in local process than on the destination brick process most
of the times. For all the entries pump finds in readdir it does a
lookup. During this lookup the entry on the destination brick is
created and healed. This is the reason why replace-brick
succeeds whenever read-child for the directory is chosen as the
source-brick. Which is most of the times. When read-child is chosen
as the destination brick, readdir returns no entries so replace-brick
completes without syncing the whole data.
Fix:
Set readdir-size in pump so that entry self-heal happens with
64k size. This ensures that entry self-heal triggered from
opendir actually creates the files on the destination brick.
Change-Id: I65ea45d3c2735a9578f3aa34eff771b6563241ca
BUG: 909800
Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
Reviewed-on: http://review.gluster.org/4712
Tested-by: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Anand Avati <avati@redhat.com>
Diffstat (limited to 'api')
0 files changed, 0 insertions, 0 deletions