-
Notifications
You must be signed in to change notification settings - Fork 82
How to set/visualize volume options #1183
Comments
Yes, currently GD2 uses a different way of setting the xlator options but #816 will address this issue. But in case you are using - curl -XPOST http://localhost:24007/v1/volumes/test01/options curl -XGET http://localhost:24007/v1/volumes/test01/options
I am not entirely sure why you get an empty response to the above request as there are some xlator options that are set by default which should be returned as an output.
Please try something like - In case, I have missed out on something or you have any other issue please do notify. |
hi @vpandey-RH i have successfully added the option you suggested however the GET command still returning empty as '405 Method Not Allowed':
do i miss something? |
@labazza Can you update your GD2 to the latest version - v4.1.0-152.git353e236 and try the above request again. |
@kshlm can we get updated glusterd2 from this repo |
@labazza The version of GD2 you're using (v4.1.0) does not support getting just the options from ReST (GET /v1/volumes/volume/options). This was introduced in a later commit. If you want to, you can try out the nightly rpms which have the Get options API available. Please note that GD2 is still under heavy development, and the official builds available via the distro repositories will not always be up-to-date. |
@labazza did you get a chance to test the latest nightly? |
I have moved to glusterd, and been busy with that deployment. I will setup glusterd2 on a VM and continue testing. If you want this can be archived. thanks |
Observed behavior
the volume options used in glusterd do not appear to have the same name in glusterd2, i couldn't visualize them either. Example options:
performance.readdir-ahead: on
diagnostics.client-log-level: WARNING
...
Expected/desired behavior
glustercli volume set volname performance.readdir-ahead on
and the option is set
glustercli volume info volname
and some options are displayed
glustercli volume set volumename TAB completion of the option
glustercli options list
to retrieve all the options
Details on how to reproduce (minimal and precise)
curl -i -X GET http://localhost:24007/v1/volumes/test01/options
returns empty if no options exist
glustercli volume set test01 performance.io-thread-count 32
Volume option set failed
Error: Request failed with HTTP Status code 500
Transaction step vol-option.Validate failed on peer 7a6c5914-3b72-49f6-9bf8-018e90c7d5c7 with error: Validation failed for volume option: option not found: performance.io-thread-count
Information about the environment:
Glusterd2 version used (e.g. v4.1.0 or master): {"glusterd-version":"v4.1.0-0","api-version":1}
Operating system used: centos 7.5.1804
Glusterd2 compiled from sources, as a package (rpm/deb), or container: from repo: https://buildlogs.centos.org/centos/7/storage/x86_64/gluster-4.1/
Using External ETCD: (yes/no, if yes ETCD version): no
If container, which container image:
Using kubernetes, openshift, or direct install:
If kubernetes/openshift, is gluster running inside kubernetes/openshift or outside:
Other useful information
the other thing is that there is nothing related to API calls in /var/log/glusterd2/glusterd2.log
uuid.toml
from all nodes (default /var/lib/glusterd2/uuid.toml)statedump
from any one of the nodeUseful commands
statedump.txt
The text was updated successfully, but these errors were encountered: