[Bugs] [Bug 1231837] New: bitrot: (rfe) object signing wait time value should be tunable.

[bugzilla at redhat.com]

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

            Bug ID: 1231837
           Summary: bitrot: (rfe) object signing wait time value should be
                    tunable.
           Product: Red Hat Gluster Storage
           Version: 3.1
         Component: glusterfs
     Sub Component: bitrot
          Assignee: rhs-bugs at redhat.com
          Reporter: ggarg at redhat.com
        QA Contact: rmekala at redhat.com
                CC: bugs at gluster.org, rmekala at redhat.com
        Depends On: 1228680
            Blocks: 1231832



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

Description of problem:

Currently bitrot using 120 sec wait time for object to signing after releasing
all the fops. This waiting time value should be tunable for QA testing.

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

--- Additional comment from Anand Avati on 2015-06-05 08:49:41 EDT ---

REVIEW: http://review.gluster.org/11105 (features/bitrot: tuanble object
signing waiting time value for bitrot) posted (#1) for review on master by
Gaurav Kumar Garg (ggarg at redhat.com)

--- Additional comment from Anand Avati on 2015-06-11 09:39:59 EDT ---

REVIEW: http://review.gluster.org/11105 (features/bitrot: tuanble object
signing waiting time value for bitrot) posted (#4) for review on master by
Gaurav Kumar Garg (ggarg at redhat.com)

--- Additional comment from Anand Avati on 2015-06-11 10:07:58 EDT ---

REVIEW: http://review.gluster.org/11105 (features/bitrot: tuanble object
signing waiting time value for bitrot) posted (#5) for review on master by
Gaurav Kumar Garg (ggarg at redhat.com)

--- Additional comment from Anand Avati on 2015-06-12 06:29:50 EDT ---

REVIEW: http://review.gluster.org/11105 (features/bitrot: tuanble object
signing waiting time value for bitrot) posted (#7) for review on master by
Venky Shankar (vshankar at redhat.com)

--- Additional comment from Anand Avati on 2015-06-12 06:51:17 EDT ---

REVIEW: http://review.gluster.org/11105 (features/bitrot: tuanble object
signing waiting time value for bitrot) posted (#8) for review on master by
Venky Shankar (vshankar at redhat.com)

--- Additional comment from Anand Avati on 2015-06-15 02:30:01 EDT ---

REVIEW: http://review.gluster.org/11105 (features/bitrot: tuanble object
signing waiting time value for bitrot) posted (#9) for review on master by
Gaurav Kumar Garg (ggarg at redhat.com)

--- Additional comment from Anand Avati on 2015-06-15 08:23:52 EDT ---

COMMIT: http://review.gluster.org/11105 committed in master by Venky Shankar
(vshankar at redhat.com) 
------
commit 554fa0c1315d0b4b78ba35a2d332d7ac0fd07d48
Author: Gaurav Kumar Garg <ggarg at redhat.com>
Date:   Fri Jun 5 13:58:28 2015 +0530

    features/bitrot: tuanble object signing waiting time value for bitrot

     Currently bitrot using 120 second waiting time for object to be signed
     after all fop's released. This signing waiting time value should be
tunable.

     Command for changing the signing waiting time will be
     #gluster volume bitrot <VOLNAME> signing-time <waiting time value in
second>

    Change-Id: I89f3121564c1bbd0825f60aae6147413a2fbd798
    BUG: 1228680
    Signed-off-by: Gaurav Kumar Garg <ggarg at redhat.com>
    Signed-off-by: Venky Shankar <vshankar at redhat.com>
    Reviewed-on: http://review.gluster.org/11105


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1228680
[Bug 1228680] bitrot: (rfe) object signing wait time value should be
tunable.
https://bugzilla.redhat.com/show_bug.cgi?id=1231832
[Bug 1231832] bitrot: (rfe) object signing wait time value should be
tunable.
-- 
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=JTBw2JiCUn&a=cc_unsubscribe