| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Change-Id: Ic765ede72eacd03501549e71247265aa86983d86
Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
It's not clear why this started failing after the last merge, since the
mem_acct code hasn't changed for a while, but it did and having those
functions is good form anyway.
Also removed a bunch of GF_ASSERT(0) calls that made (and will continue
to make) debugging unnecessarily painful.
Change-Id: Icd89f2e23f1eaafc79cb9af06c3c9c8d2fdeec14
Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Failure to do this was causing the event to be propagated up to DHT,
which would then decide that the entire NSR subvolume was down. Then
weird things would happen, such as (the example that tipped me off)
directory listings showing stale data without the readdir* calls even
getting down to NSR.
Handling of CHILD_UP/CHILD_DOWN still needs to be improved, but this
will do for now.
Change-Id: Id85d5976231df9cb2c4af59b3aaa82cedb14f54f
Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
|
|
|
|
|
| |
Change-Id: I6c365ddedc3e96a67127cf012819e9a0138395f4
Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
|
|
Previous history:
https://forge.gluster.org/~jdarcy/glusterfs-core/glusterfs-nsr
Change-Id: I2b56328788753c6a74d9589815f2dd705ac9ce6a
Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
|