This is still bothering us a lot and looks like there is a genuine issue in
the code which is making the the process to be hung/deadlocked?
Raghavendra T - any more findings?
On Friday 19 August 2016, Atin Mukherjee wrote:
>
On 08/27/2016 12:15 PM, Niels de Vos wrote:
On Sat, Aug 27, 2016 at 08:52:11PM +0530, Aravinda wrote:
Hi,
As part of Client events support, glustereventsd needs to be configured to
use a port. Following ports are already used by Gluster components.
24007 For glusterd
24008
On Sat, Aug 27, 2016 at 08:52:11PM +0530, Aravinda wrote:
> Hi,
>
> As part of Client events support, glustereventsd needs to be configured to
> use a port. Following ports are already used by Gluster components.
> 24007 For glusterd
> 24008 For glusterd RDMA port management
>
Updated. We have couple of enhancements in Geo-replication too. I will
send pull request to update the Geo-rep enhancements.
regards
Aravinda
On Friday 26 August 2016 09:39 PM, Pranith Kumar Karampuri wrote:
On Fri, Aug 26, 2016 at 9:38 PM, Pranith Kumar Karampuri
Hi,
As part of Client events support, glustereventsd needs to be configured
to use a port. Following ports are already used by Gluster components.
24007 For glusterd
24008 For glusterd RDMA port management
38465 Gluster NFS service
38466 Gluster NFS service
Oops!
Didn't noticed these changes were part of parent/child patches, Just
noticed "BUILD BROKEN" and went into action :)
I'm not sure about it!
If it takes time to decide on whether the other set of patches need to
be taken or not, at-least my patch will fix the broken build (That
much I can
On Saturday 27 August 2016, Prasanna Kalever wrote:
> Here is the patch that should fix it
> http://review.gluster.org/#/c/15331/
Thanks! Well thats an easy way, but the question here is dont we need the
parent patch to be merged to ensure there is no other functionality
Here is the patch that should fix it
http://review.gluster.org/#/c/15331/
Happy weekend!
--
Prasanna
On Sat, Aug 27, 2016 at 7:49 PM, Atin Mukherjee wrote:
> [1] has broken mainline compilation and I feel this could be because its
> parent patch is not been merged
[1] has broken mainline compilation and I feel this could be because its
parent patch is not been merged otherwise smoke should have caught it.
Please resolve it at earliest.
[1] http://review.gluster.org/#/c/15225/
--Atin
___
Gluster-devel mailing
- Original Message -
> From: "Pranith Kumar Karampuri"
> To: "Rajesh Joseph" , "Manikandan Selvaganesh"
> , "Csaba Henk"
> , "Niels de Vos" , "Jiffin Thottan"
> ,
10 matches
Mail list logo