[Bugs] [Bug 1272409] New: Data Tiering:Lot of Promotions/Demotions failed error messages

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1272409

            Bug ID: 1272409
           Summary: Data Tiering:Lot of Promotions/Demotions failed error
                    messages
           Product: Red Hat Gluster Storage
         Component: glusterfs
     Sub Component: tiering
          Severity: urgent
          Priority: urgent
          Assignee: rhs-bugs at redhat.com
          Reporter: nchilaka at redhat.com
        QA Contact: nchilaka at redhat.com
                CC: bugs at gluster.org
        Depends On: 1272398
            Blocks: 1260923



+++ This bug was initially created as a clone of Bug #1272398 +++

Description of problem:
======================
On QE Setups like the one used for longevity and stress, we are seeing lot of
promote/demote failed error messages in tier log.
If they are genuine, then we need to find the reason and fix them accordingly.
If they are spurious errors, we need to clean up such errors before the product
release, as it is really difficult for debugging or root causing other issues



Version-Release number of selected component (if applicable):
=======================================================
glusterfs-server-3.7.5-0.19.git0f5c3e8.el7.centos.x86_64

Steps Carried:
==============

1. Created 12 node cluster
2. Create tiered volume with Hot tier as (6 x 2) and Cold tier as (2 x (6 + 2)
= 16)
3. Fuse Mount the volume on 3 clients RHEL7.2,RHEl7.1 and RHEL6.7
4. Start creating data from each client:

Client 1:
=========
[root at dj ~]# crefi --multi -n 10 -b 10 -d 10 --max=1024k --min=5k --random -T 5
-t text -I 5 --fop=create /mnt/fuse/

Client 2:
=========
[root at mia ~]# cd /mnt/fuse/
[root at mia fuse]# for i in {1..10}; do cp -rf /etc etc.$i ; sleep 100 ; done

Client 3:
=========
[root at wingo fuse]# for i in {1..999}; do dd if=/dev/zero of=dd.$i bs=1M count=1
; sleep 10 ; done

5. After a while, the data creation of client 1 and client 2 should be
completed while the data creation from client 3 will still be inprogress

6. At this point the data creation will be of only 1 file from client 3 in
every 10 sec.

7. Monitor the cpu usage using top


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1260923
[Bug 1260923] Tracker for tiering in 3.1.2
https://bugzilla.redhat.com/show_bug.cgi?id=1272398
[Bug 1272398] Data Tiering:Lot of Promotions/Demotions failed error
messages
-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=C7FsUD1I33&a=cc_unsubscribe