[Bugs] [Bug 1226146] New: BitRot :- bitd is not signing Objects if more than 3 bricks are present on same node

[bugzilla at redhat.com]

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

            Bug ID: 1226146
           Summary: BitRot :- bitd is not signing Objects if more than 3
                    bricks are present on same node
           Product: GlusterFS
           Version: 3.7.0
         Component: bitrot
          Keywords: Triaged
          Severity: high
          Priority: high
          Assignee: bugs at gluster.org
          Reporter: vshankar at redhat.com
                CC: bugs at gluster.org, hchiramm at redhat.com,
                    mzywusko at redhat.com, nsathyan at redhat.com,
                    rabhat at redhat.com, racpatel at redhat.com,
                    vshankar at redhat.com
        Depends On: 1207134
            Blocks: 1186580 (qe_tracker_everglades), 1219955
                    (glusterfs-3.7.1), 1221560, 1221605, 1224182, 1224193
      Docs Contact: bugs at gluster.org




Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1186580
[Bug 1186580] QE tracker bug for Everglades
https://bugzilla.redhat.com/show_bug.cgi?id=1207134
[Bug 1207134] BitRot :- bitd is not signing Objects if more than 3 bricks
are present on same node
https://bugzilla.redhat.com/show_bug.cgi?id=1219955
[Bug 1219955] GlusterFS 3.7.1 tracker
https://bugzilla.redhat.com/show_bug.cgi?id=1221560
[Bug 1221560] `-bash: fork: Cannot allocate memory' error seen regularly on
nodes on execution of any command
https://bugzilla.redhat.com/show_bug.cgi?id=1221605
[Bug 1221605] Scrub.log grows rapidly and the size increases upto 24GB in a
span of 10 hours
https://bugzilla.redhat.com/show_bug.cgi?id=1224182
[Bug 1224182] `-bash: fork: Cannot allocate memory' error seen regularly on
nodes on execution of any command
https://bugzilla.redhat.com/show_bug.cgi?id=1224193
[Bug 1224193] Scrub.log grows rapidly and the size increases upto 24GB in a
span of 10 hours
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are the Docs Contact for the bug.