Skip to content
This repository has been archived by the owner on Mar 26, 2020. It is now read-only.

Issues: gluster/glusterd2

195 Open 507 Closed
195 Open 507 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Is glusterd2 dead?
#1512 opened Aug 15, 2019 by ateleshev
8
Please fix systemd depency to rpcbind in progress
#1509 opened Mar 29, 2019 by zem
@kshlm
1
Can gd2 take a directory as requirement (instead of 'add-device') for loopback bricks?
#1502 opened Mar 7, 2019 by amarts
2
GlusterD kubernetes: systemctl start glusterd silent failures.
#1496 opened Feb 4, 2019 by jayunit100
1
Brick process didn't come up on the node post gluster node reboot bug
#1492 opened Jan 23, 2019 by PrasadDesala
2
PVC delete failed to delete 146/250 gluster volumes
#1489 opened Jan 22, 2019 by PrasadDesala
Volume status shows PID as 0 for few volumes
#1487 opened Jan 21, 2019 by PrasadDesala
1
parallel volume deletion requests fail with device or resource busy for some of the PVs brick-multiplexing-issue tracker label to capture all issues related to brick multiplexing feature bug priority: high
#1479 opened Jan 14, 2019 by atinmu
@oshankkumar
1
Inconsistency in glustershd process bug priority: high
#1474 opened Jan 10, 2019 by Shrivaibavi
@vpandey-RH
1
stale brick process when volume stop operations are done in parallel in brick multiplexing mode brick-multiplexing-issue tracker label to capture all issues related to brick multiplexing feature bug priority: high
#1470 opened Jan 8, 2019 by atinmu
8
Fix spurious socket connect failure issue in brick multiplexing stop code path brick-multiplexing-issue tracker label to capture all issues related to brick multiplexing feature in progress priority: high
#1468 opened Jan 8, 2019 by atinmu
@atinmu @vpandey-RH
1
glustershd memory keeps increasing while creating PVCs
#1467 opened Jan 7, 2019 by PrasadDesala
11
Healinfo for disperse volumes errors out priority: low
#1465 opened Jan 7, 2019 by shtripat
3
glustershd needs to be restarted for volume start/stop operations bug FW: Daemon Management priority: high
#1459 opened Jan 3, 2019 by atinmu
@rafikc30
1
Bricks are failing to connect to the volume post gluster node reboot brick-multiplexing-issue tracker label to capture all issues related to brick multiplexing feature bug priority: high
#1457 opened Jan 3, 2019 by PrasadDesala
@oshankkumar
7
Mechanism to suppress repetitive logs FW: Logging priority: high
#1456 opened Jan 3, 2019 by atinmu
@harigowtham
1
volume info shows the volume state as started but volume status shows it as offline brick-multiplexing-issue tracker label to capture all issues related to brick multiplexing feature bug
#1452 opened Jan 2, 2019 by PrasadDesala
@vpandey-RH
3
Old brick process is still running after volume reset -> stop -> start brick-multiplexing-issue tracker label to capture all issues related to brick multiplexing feature bug priority: low
#1451 opened Jan 2, 2019 by PrasadDesala
4
Continuous "0-epoll: Failed to dispatch handler" errors in brick logs
#1450 opened Jan 2, 2019 by PrasadDesala
6
stale sockets fds under brick process brick-multiplexing-issue tracker label to capture all issues related to brick multiplexing feature bug priority: medium
#1449 opened Jan 2, 2019 by PrasadDesala
1
sos reports should collect all necessary gd2 logs FW: Logging priority: medium
#1448 opened Jan 2, 2019 by PrasadDesala
1
"glustercli volume get" help needs to be more clear FW: CLI priority: low
#1444 opened Dec 28, 2018 by PrasadDesala
Commands to get healed entries & entries on which heal failed information for the volumes in gd2
#1442 opened Dec 27, 2018 by Shrivaibavi
@vpandey-RH
2
glustercli peer list and peer status displays same output priority: low
#1441 opened Dec 27, 2018 by PrasadDesala
2
Device info is not listed on the nodes after peer detach bug FW: Device Management priority: medium
#1440 opened Dec 27, 2018 by PrasadDesala
@rishubhjain
ProTip! Find all open issues with in progress development work with linked:pr.