Bug 1277627 - tiering: demotion are not happening when quota limit is reached
tiering: demotion are not happening when quota limit is reached
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: tier (Show other bugs)
x86_64 Linux
unspecified Severity urgent
: ---
: ---
Assigned To: Vijaikumar Mallikarjuna
Anil Shah
: ZStream
Depends On:
Blocks: 1260783 1260923
  Show dependency treegraph
Reported: 2015-11-03 11:52 EST by Anil Shah
Modified: 2016-09-17 11:42 EDT (History)
8 users (show)

See Also:
Fixed In Version: glusterfs-3.7.5-6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-12-09 23:21:00 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Anil Shah 2015-11-03 11:52:22 EST
Description of problem:

When quota limit is exceeded, demotion of files are not happening.

Version-Release number of selected component (if applicable):

[root@localhost ec01]# rpm -qa | grep glusterfs

How reproducible:


Steps to Reproduce:

1. Created 2*2 distribute replicate volume
2. Fuse mount the volume 
3. Set quota on volume 
4. Create file on the so that disk quota exceeds 
5. Now attach 2*2 distribute replicate tier
6. Modify the quota limit
7. Enable ctr, tier-promote, tier-demote frequency 
7. Create some files from mount point. 
8. Wait for demotion to happen
9. Read one of the file from Mount point
10. Wait for demotion to happen after specified time

log for tier file

r-dht: ERROR in current lookup

[2015-11-03 22:15:45.119783] E [MSGID: 109037] [tier.c:1488:tier_start] 0-testvol-tier-dht: Demotion failed
The message "E [MSGID: 109037] [tier.c:463:tier_migrate_using_query_file] 0-testvol-tier-dht: ERROR in current lookup
" repeated 2 times between [2015-11-03 22:15:45.119374] and [2015-11-03 22:17:15.268892]
The message "E [MSGID: 109037] [tier.c:1488:tier_start] 0-testvol-tier-dht: Demotion failed" repeated 2 times between [2015-11-03 22:15:45.119783] and [2015-11-03 22:17:15.269204]
Actual results:

Demotion doesn't happen

Expected results:

Demotion of file should happen, Restarted the volume and demotion started to happen 

Additional info:

[root@localhost ec01]# gluster v info
Volume Name: testvol
Type: Tier
Volume ID: fbee6a2e-39ef-4388-8239-8a148dafdba9
Status: Started
Number of Bricks: 8
Transport-type: tcp
Hot Tier :
Hot Tier Type : Distributed-Replicate
Number of Bricks: 2 x 2 = 4
Cold Tier:
Cold Tier Type : Distributed-Replicate
Number of Bricks: 2 x 2 = 4
Options Reconfigured:
features.barrier: disable
cluster.tier-promote-frequency: 45
cluster.tier-demote-frequency: 45
cluster.write-freq-threshold: 0
cluster.read-freq-threshold: 0
Comment 4 Manikandan 2015-11-19 05:56:59 EST
We are not able to reproduce the problem in the current build. Can you try to reproduce it in the current build?

Manikandan Selvaganesh.
Comment 5 nchilaka 2015-11-25 00:40:24 EST
if the bug is not reproducible, we must be moving it to "works for me".
Please contact the reporter and find out what was the exact scenario and setup used for raising this bug.
If you are still not able to reproduce, but the pertaining logs and move to "works for me"

only Bugs which have code fix through a patch for the same problem must be moved to on_QA
Comment 7 Anil Shah 2015-12-09 23:21:00 EST
Not able to reproduce this bug on latest build. Seeing demotions happening on files. Will open a new bug once encountered issue again.

Hence closing this bug as of now.
Comment 8 nchilaka 2015-12-14 06:28:20 EST
This has been closed by QE as not reproducible, but this can be a "potential risk"
Also, if it was moved to post, why not have the fix in?

Note You need to log in before you can comment on or make changes to this bug.