You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 26, 2020. It is now read-only.
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
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}
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
glusterd2 config files from all nodes (default /etc/glusterd2/glusterd2.toml)
glusterd2 log files from all nodes (default /var/log/glusterd2/glusterd2.log)
the other thing is that there is nothing related to API calls in /var/log/glusterd2/glusterd2.log
ETCD configuration
Contents of uuid.toml from all nodes (default /var/lib/glusterd2/uuid.toml)
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.tomlfrom all nodes (default /var/lib/glusterd2/uuid.toml)statedumpfrom any one of the nodeUseful commands
statedump.txt