Bug 1290787
| Summary: | [tiering]: Hexadecimal values accepted in read/write counters | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Sweta Anandpara <sanandpa> |
| Component: | tier | Assignee: | hari gowtham <hgowtham> |
| Status: | CLOSED WONTFIX | QA Contact: | Nag Pavan Chilakam <nchilaka> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rhgs-3.1 | CC: | annair, rcyriac, rhs-bugs, sanandpa, sankarshan, sasundar |
| Target Milestone: | --- | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-02-06 17:43:17 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Sweta Anandpara
2015-12-11 13:11:52 UTC
1. 0xd would result in a similar output as seen in the logs above, for 0xffff [root@dhcp37-55 ~]# gluster v set nash cluster.write-freq-threshold 0xd volume set: success [root@dhcp37-55 ~]# gluster v get nash cluster.write-freq-threshold Option Value ------ ----- cluster.write-freq-threshold 0xd [root@dhcp37-55 ~]# 2. Yes, decimal values are known to be accepted, and they are (as mentioned in the description above). That is what has been tested until now. Karthick's observation: Even negative values are accepted [root@dhcp37-55 ~]# gluster v set nash cluster.write-freq-threshold -4 volume set: success [root@dhcp37-55 ~]# gluster v get nash cluster.write-freq-threshold Option Value ------ ----- cluster.write-freq-threshold -4 [root@dhcp37-55 ~]# I am aware of some more options, where values are accepted as hexadecimal or octal. I thought that was the standard behavior though. Few of the volume options as I know are below, [root@ ~]# gluster volume set Gluster-Vol-2 high-prio-threads 0xf volume set: success [root@ ~]# gluster volume set Gluster-Vol-2 performance.cache-size 0xffff volume set: success [root@ ~]# gluster volume get Gluster-Vol-2 performance.cache-size Option Value ------ ----- performance.cache-size 0xffff [root@ ~]# gluster volume set Gluster-Vol-2 high-prio-threads 071 volume set: success [root@ ~]# gluster volume get Gluster-Vol-2 high-prio-threads Option Value ------ ----- performance.high-prio-threads 071 So, I would call for action to set a standard behavior for all volume options either accepting hexadecimal, decimal & octal values or only decimal values. Thank you for your bug report. We are no longer working on any improvements for Tier. This bug will be set to CLOSED WONTFIX to reflect this. Please reopen if the rfe is deemed critical. |