7ec3a8527f
When eager-lock lock acquisition fails because of say network failures, the local is not being removed from owners_list, this leads to accumulation of waiting frames and the application will hang because the waiting frames are under the assumption that another transaction is in the process of acquiring lock because owner-list is not empty. Handled this case as well in this patch. Added asserts to make it easier to find these problems in future. fixes bz#1699731 Change-Id: I3101393265e9827755725b1f2d94a93d8709e923 Signed-off-by: Pranith Kumar K <pkarampu@redhat.com> |
||
---|---|---|
.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.