glusterfs.git/glusterfsd, branch v8.1

posix: Implement a janitor thread to close fd

2020-08-21T10:38:07+00:00

Problem: In the commit fb20713b380e1df8d7f9e9df96563be2f9144fd6 we use
         syntask to close fd but we have found the patch is reducing the
         performance

Solution: Use janitor thread to close fd's and save the pfd ctx into
          ctx janitor list and also save the posix_xlator into pfd object to
          avoid the race condition during cleanup in brick_mux environment

Change-Id: Ifb3d18a854b267333a3a9e39845bfefb83fbc092
Fixes: #1396
Signed-off-by: Mohit Agrawal 
(cherry picked from commit 41b9616435cbdf671805856e487e373060c9455b)

glusterfsd: structure logging

2020-02-06T05:27:03+00:00

convert gf_msg() to gf_smsg()

Change-Id: I1cd6a5ac6f4361195d5d925efb2cc194045d0bba
Updates: #657
Signed-off-by: yatip

multiple xlators: reduce key length

2020-01-14T17:11:22+00:00

In many cases, we were freely allocating long keys with no need.
Smaller char arrays are just fine almost anywhere, so just went ahead
and looked where they we can use smaller ones.

In some cases, annotated the functions as static and the prefixes
passed as const as it was easier to read and understand.

Where relevant, converted the dict functions to use known key length.

Change-Id: I882ab33ea20d90b63278336cd1370c09ffdab7f2
updates: bz#1193929
Signed-off-by: Yaniv Kaul

mgmt/brick-mux: Avoid sending two response when attach is failed.

2019-12-31T13:35:10+00:00

We were sending two response back to glusterd when an attach is
failed. One from the handler function glusterfs_handle_attach and
another from rpcsvc_check_and_reply_error. It was causing problems
like ref leaks, transport disconnect etc.

Change-Id: I3bb5b59959530760b568d52becb519499b3dcd2b
updates: bz#1785143
Signed-off-by: Mohammed Rafi KC

glusterd: refactoring long method

2019-12-19T09:10:01+00:00

- Refactored set_fuse_mount_options(...) in order to shorten it.
- Removed dead code and moved some method to it's apropriate
location.
- Converted loggin in set_fuse_mount_options(...) to structured logs

fixes: bz#1768896
Change-Id: If865833d4c60d517da202871978691ef21235fe4
Signed-off-by: Barak Sason Rofman

[RFC]#ifdef gNFS related code if we are not compiling gNFS

2019-12-18T03:47:42+00:00

If we are not compiling gNFS (--enable-gnfs is not given in the
./configure script params), there is little point in compiling code
that is related to it.

This patch tries to eliminate it.
My hope (and it's not clear from the code ) is that I did not break
the NFS Ganesha support as well.

Other than that, tried to compile with and without anad it looks sane.

Change-Id: I8d6c98066b9fceab4ec10fc6f5e81ab069e853bd
updates: bz#1193929
Signed-off-by: Yaniv Kaul

glusterfsd.c: remove sys_lstat() call

2019-11-27T07:21:10+00:00

get_volfp() in glfs.c doesn't use it, so get_volfp() in glusterfsd.c
can just open the file without the stat call as well, IMHO.

Change-Id: I3cb5bf12a09b5be42aa2ee4f432f8d351eee5b9e
updates: bz#1193929
Signed-off-by: Yaniv Kaul

glusterfsd-mgmt.c: move INFO log outside a LOCK

2019-11-19T10:03:28+00:00

In glusterfs_handle_attach() we can:
1. Move an INFO level to be executed before the LOCK.
2. Skip the LOCK altogether, if there's no active graph.

I hope it's safe - I've seen that in other functions
you could look at ctx->active outside of a lock.

Change-Id: I3e1ec5b1430d5fddee46883d468ff4f5bd6ca54b
updates: bz#1193929
Signed-off-by: Yaniv Kaul

[WIP]gluster-volgen.c: remove more of JBR and FDL xlators

2019-11-13T06:30:24+00:00

the JBR and FDL experimental xlators were apparently removed.
Removed additional leftovers scattered in the code.

Change-Id: I78b6fa5fd9044dc48cdcb1fb094b8c267c2d1323
updates: bz#1193929
Signed-off-by: Yaniv Kaul

gluster: check ctx->active

2019-11-12T14:08:36+00:00

To avoid process "TRANSLATOR INFO" "BARRIER" if graph is not ready,
also see commit ee630e25.

Updates: bz#1769712
Signed-off-by: Xie Changlong 
Change-Id: Ibd446a35962206d3689667cda7e6712d72e4ec2f