4d9935a4db
In the case socket read returns EAGAIN, positive value about remaining vector to send is returned. This return value will be passed all the way back to event handler, making it complains. [2018-12-29 08:02:25.603199] T [socket.c:1640:__socket_read_simple_payload] 0-test-client-0-extra.0: partial read on non-blocking socket. [2018-12-29 08:02:25.603201] T [rpc-clnt.c:654:rpc_clnt_reply_init] 0-test-client-2-extra.1: received rpc message (RPC XID: 0xfa6 Program: GlusterFS 4.x v1, ProgVers: 400, Proc: 12) from rpc-transport (test-client-2-extra.1) [2018-12-29 08:02:25.603207] T [socket.c:3129:socket_event_handler] 0-test-client-0-extra.0: (sock:32) socket_event_poll_in returned 1 Formerly, in socket_proto_state_machine, return value of socket_readv is used to check if message is all read-in. In this commit, it is checked whether size of bytes indicated in header are all read in. In this way, only 0 and -1 will be returned from socket_proto_state_machine(), indicating whether there is error in the underlying socket. Change-Id: I8be0d178b049f0720d738a03aec41c4b375d2972 updates: bz#1666143 Signed-off-by: Zhang Huan <zhanghuan@open-fs.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.