491ff40a7a
With commit#ad35193,we have made changes to offload processing upcall notifications to synctask so as not to block epoll threads. However seems like the issue wasnt fully addressed. In "glfs_cbk_upcall_data" -> "synctask_new1" after creating synctask if there is no callback defined, the thread waits on synctask_join till the syncfn is finished. So that way even with those changes, epoll threads are blocked till the upcalls are processed. Hence the right fix now is to define a callback function for that synctask "glfs_cbk_upcall_syncop" so as to unblock epoll/notify threads completely and the upcall processing can happen in parallel by synctask threads. Change-Id: I4d8645e3588fab2c3ca534e0112773aaab68a5dd fixes: bz#1694561 Signed-off-by: Soumya Koduri <skoduri@redhat.com> (cherry picked from commit 4a03a71c6171f6e8382664d9d29857d06ef37741) |
||
---|---|---|
.github | ||
api | ||
build-aux | ||
cli | ||
contrib | ||
doc | ||
events | ||
extras | ||
geo-replication | ||
glusterfsd | ||
heal | ||
libglusterfs | ||
rpc | ||
tests | ||
tools | ||
xlators | ||
.clang-format | ||
.gitignore | ||
.mailmap | ||
.testignore | ||
AUTHORS | ||
autogen.sh | ||
ChangeLog | ||
COMMITMENT | ||
configure.ac | ||
CONTRIBUTING | ||
COPYING-GPLV2 | ||
COPYING-LGPLV3 | ||
glusterfs-api.pc.in | ||
glusterfs.spec.in | ||
INSTALL | ||
libgfchangelog.pc.in | ||
libgfdb.pc.in | ||
MAINTAINERS | ||
Makefile.am | ||
NEWS | ||
README.md | ||
rfc.sh | ||
run-tests-in-vagrant.sh | ||
run-tests.sh | ||
site.h.in | ||
submit-for-review.sh | ||
THANKS |
Gluster
Gluster is a software defined distributed storage that can scale to several petabytes. It provides interfaces for object, block and file storage.
Development
Contributions to gluster in the form of patches and new feature additions can be made by following steps outlined at Developers Guide.
Documentation
The Gluster documentation can be found at Gluster Docs.
Deployment
Quick instructions to build and install can be found in INSTALL file.
Testing
GlusterFS source contains some functional tests under tests/
directory. All
these tests are run against every patch submitted for review. If you want your
patch to be tested, please add a .t
test file as part of your patch submission.
You can also submit a patch to only add a .t
file for the test case you are
aware of.
To run these tests, on your test-machine, just run ./run-tests.sh
. Don't run
this on a machine where you have 'production' glusterfs is running, as it would
blindly kill all gluster processes in each runs.
If you are sending a patch, and want to validate one or few specific tests, then run a single test by running the below command.
bash# /bin/bash ${path_to_gluster}/tests/basic/rpc-coverage.t
You can also use prove
tool if available in your machine, as follows.
bash# prove -vmfe '/bin/bash' ${path_to_gluster}/tests/basic/rpc-coverage.t
Maintainers
The list of Gluster maintainers is available in MAINTAINERS file.
License
Gluster is dual licensed under GPLV2 and LGPLV3+.
Please visit the Gluster Home Page to find out more about Gluster.