glusterfs.git/xlators/protocol/client/src, branch release-9

xlators: misc conscious language changes (#1715)

2020-11-02T12:33:01+00:00

core:change xlator_t->ctx->master to xlator_t->ctx->primary
afr: just changed comments.
meta: change .meta/master to .meta/primary. Might break scripts.
changelog: variable/function name changes only.

These are unrelated to geo-rep.
Fixes: #1713

Change-Id: I58eb5fcd75d65fc8269633acc41313503dccf5ff
Signed-off-by: Ravishankar N

cluster/dht: Perform migrate-file with lk-owner (#1581)

2020-10-29T04:22:20+00:00

* cluster/dht: Perform migrate-file with lk-owner

1) Added GF_ASSERT() calls in client-xlator to find these
issues sooner.
2) Fuse is setting zero-lkowner with len as 8 when the fop
doesn't have any lk-owner. Changed this to have len as 0
just as we have in fops triggered from xlators lower to
fuse.

* syncop: Avoid frame allocation if we can
* cluster/dht: Set lkowner in daemon rebalance code path
* cluster/afr: Set lkowner for ta-selfheal
* cluster/ec: Destroy frame after heal is done
* Don't assert for lk-owner in lk call
* set lkowner for mandatory lock heal tests

fixes: #1529
Change-Id: Ia803db6b00869316893abb1cf435b898eec31228
Signed-off-by: Pranith Kumar K

protocol/client: fallback to anonymous fd for fsync

2020-03-06T01:54:02+00:00

Change-Id: I32f801206ce7fbd05aa693f44c2f140304f2e275
Fixes: bz#1810842

protocol/client: structure logging

2020-02-03T12:06:00+00:00

convert gf_msg() to gf_smsg()

Updates: #657

Change-Id: I76a09cfd283bb4ec5c4358536da66547aaf0de31
Signed-off-by: yatip

dht: Fix stale-layout and create issue

2019-12-27T06:36:19+00:00

Problem: With lookup-optimize set to on by default, a client with
stale-layout can create a new file on a wrong subvol. This will lead to
possible duplicate files if two different clients attempt to create the
same file with two different layouts.

Solution: Send in-memory layout to be cross checked at posix before
commiting a "create". In case of a mismatch, sync the client layout with
that of the server and attempt the create fop one more time.

test: Manual, testcase(attached)

fixes: bz#1786679
Change-Id: Ife0941f105113f1c572f4363cbcee65e0dd9bd6a
Signed-off-by: Susant Palai

protocol/client-rpc-fops: structure logging

2020-01-30T13:29:54+00:00

convert all gf_msg() to gf_smsg()

Updates: #657

Change-Id: Ia9d4fb17579af6586bc13d69ec7990c6cf220aac
Signed-off-by: yatip

protocol/client: Maintain connection to brick status

2020-02-04T09:13:35+00:00

Problem:
The current version of the code depends on the non-zero-port information to
propagate ping event from brick to parent layers. But as and when connection
succeeds, port is set to zero in rpc layer.So ping event is never propagated to
parent layers. Halo doesn't work without this.

Fix:
Remember the status of connection in 'private' structure and use that to decide
to propagate ping event to parent xlator.

fixes: bz#1797934
Change-Id: Ia578ba9fb3813953d2068dbba5c982ab27cc3429
Signed-off-by: Pranith Kumar K

protocol/client: structure logging

2020-01-29T12:32:05+00:00

convert all gf_msg() to gf_smsg()

Updates: #657

Change-Id: I69b228d7c7a8bc6263f9bd33710e880678d8c017
Signed-off-by: yatip

protocol/client-handshake: structure logging

2020-01-24T15:28:06+00:00

convert gf_msg() to gf_smsg()

Updates: #657

Change-Id: Iee07228cfc3a9a9cd10e89ae9eb918681b072585
Signed-off-by: yatip

protocol/client-rpc-fops_v2: structure logging

2020-01-24T13:31:15+00:00

convert gf_msg() to gf_smsg()

Updates: #657

Change-Id: Ib45f121f583c2af09bfddb23391f73a117e63213
Signed-off-by: yatip