Back to bug 1322306

Who When What Removed Added
Red Hat Bugzilla Rules Engine 2016-03-30 10:38:39 UTC Keywords ZStream
SATHEESARAN 2016-03-30 12:14:52 UTC Sub Component core glusterd
CC nerawat, sasundar
Component glusterfs glusterfs-server
Assignee rhs-bugs amukherj
Summary Brick process does not start after node reboot [scale] Brick process does not start after node reboot
QA Contact annair storage-qa-internal
Flags needinfo?(nerawat)
Neha 2016-03-31 05:00:51 UTC Flags needinfo?(nerawat)
Atin Mukherjee 2016-03-31 11:13:41 UTC Blocks 1322805
Atin Mukherjee 2016-03-31 11:20:42 UTC Status NEW POST
Atin Mukherjee 2016-04-04 05:57:04 UTC Blocks 1323564
Rahul Hinduja 2016-04-11 09:00:56 UTC CC rhinduja
Anoop 2016-04-26 13:36:06 UTC CC annair
Rahul Hinduja 2016-04-26 13:39:25 UTC Blocks 1311817
Rejy M Cyriac 2016-04-26 18:25:45 UTC CC rcyriac
Alok 2016-04-27 07:13:43 UTC CC asrivast
Red Hat Bugzilla Rules Engine 2016-04-27 11:22:11 UTC Target Release --- RHGS 3.1.3
Atin Mukherjee 2016-05-03 11:22:44 UTC Assignee amukherj prasanna.kalever
Prasanna Kumar Kalever 2016-05-03 13:56:47 UTC CC prasanna.kalever
Prasanna Kumar Kalever 2016-05-05 06:35:48 UTC Status POST MODIFIED
Prasanna Kumar Kalever 2016-05-06 08:00:34 UTC Blocks 1333711
Rahul Hinduja 2016-05-09 14:57:29 UTC QA Contact storage-qa-internal bsrirama
errata-xmlrpc 2016-05-10 11:25:38 UTC Status MODIFIED ON_QA
Milind Changire 2016-05-10 12:04:53 UTC Fixed In Version glusterfs-3.7.9-4
Byreddy 2016-05-16 03:46:40 UTC Status ON_QA VERIFIED
Prasanna Kumar Kalever 2016-05-16 06:48:43 UTC Doc Text Cause:
Currently glusterd selects a port number and order the brick process to bind on it, meanwhile if some other process consumes/gabs the same port, brick will of course fail to bind on the given port and refuses to come up, because there is no mechanism that brick conveys the failure to glusterd or randomly connect on some port and send this port info to glusterd

Consequence:
As a result brick will not come up, fails by reporting port already in use

Fix:
1. avoid such port clashes with client processes by segregating the available port ranges between bricks and clients

2. Provide a mechanism for brick process to report error in binding to the port given by glusterd.

Result:
Now with fix1 there are no chances that gluster (client) process will clash with brick process and in case if there is a clash with foreign process that will be handled by fix2
Prasanna Kumar Kalever 2016-05-16 07:56:42 UTC Doc Text Cause:
Currently glusterd selects a port number and order the brick process to bind on it, meanwhile if some other process consumes/gabs the same port, brick will of course fail to bind on the given port and refuses to come up, because there is no mechanism that brick conveys the failure to glusterd or randomly connect on some port and send this port info to glusterd

Consequence:
As a result brick will not come up, fails by reporting port already in use

Fix:
1. avoid such port clashes with client processes by segregating the available port ranges between bricks and clients

2. Provide a mechanism for brick process to report error in binding to the port given by glusterd.

Result:
Now with fix1 there are no chances that gluster (client) process will clash with brick process and in case if there is a clash with foreign process that will be handled by fix2
Cause:
Currently glusterd selects a port number and order the brick process to bind on it, meanwhile if some other process consumes/grabs the same port, brick will of course fail to bind on the given port and refuses to come up, because there is no mechanism that brick conveys the failure to glusterd or randomly connect on some port and send this port info to glusterd

Consequence:
As a result brick will not come up, fails by reporting port already in use

Fix:
1. avoid such port clashes with client processes by segregating the available port ranges between bricks and clients

2. Provide a mechanism for brick process to report error in binding to the port given by glusterd.

Result:
Now with fix1 there are no chances that gluster (client) process will clash with brick process and in case if there is a clash with foreign process that will be handled by fix2
Rejy M Cyriac 2016-05-25 09:47:36 UTC Blocks 1332128
Laura Bailey 2016-06-03 03:10:04 UTC Doc Text Cause:
Currently glusterd selects a port number and order the brick process to bind on it, meanwhile if some other process consumes/grabs the same port, brick will of course fail to bind on the given port and refuses to come up, because there is no mechanism that brick conveys the failure to glusterd or randomly connect on some port and send this port info to glusterd

Consequence:
As a result brick will not come up, fails by reporting port already in use

Fix:
1. avoid such port clashes with client processes by segregating the available port ranges between bricks and clients

2. Provide a mechanism for brick process to report error in binding to the port given by glusterd.

Result:
Now with fix1 there are no chances that gluster (client) process will clash with brick process and in case if there is a clash with foreign process that will be handled by fix2
Previously, if a brick attempted to bind to a port that was not available, the bind process would log an error and fail to bind to the port, but this error was not communicated back to glusterd. Different port ranges are now provided for bricks and clients by default so that clashes are less likely to occur. Additionally, in the event of clashes with other port consumers, errors of this kind are now handled more gracefully.
Flags needinfo?(prasanna.kalever)
Prasanna Kumar Kalever 2016-06-10 06:53:06 UTC CC amukherj
Flags needinfo?(prasanna.kalever) needinfo?(amukherj)
Atin Mukherjee 2016-06-10 06:57:23 UTC Flags needinfo?(amukherj)
errata-xmlrpc 2016-06-23 00:51:32 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2016-06-23 05:14:39 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2016-06-23 01:14:39 UTC
John Skeoch 2016-08-15 02:09:00 UTC CC sashinde
Rejy M Cyriac 2016-09-17 16:34:59 UTC Sub Component glusterd
Component glusterd glusterd-transition
Rejy M Cyriac 2016-09-17 16:48:22 UTC CC rhs-bugs, storage-qa-internal, vbellur
Component glusterd-transition glusterd

Back to bug 1322306