On 07/03/2015 11:58 AM, Krishnan Parthasarathi wrote:
>
>
> - Original Message -
>>
>> This is caused because when bind-insecure is turned on (which is the default
>> now), it may happen
>> that brick is not able to bind to port assigned by Glusterd for example
>> 49192-49195...
>> It s
- Original Message -
>
> This is caused because when bind-insecure is turned on (which is the default
> now), it may happen
> that brick is not able to bind to port assigned by Glusterd for example
> 49192-49195...
> It seems to occur because the rpc_clnt connections are binding to ports
> It seems this is exactly whats happening.
>
> I have a question, I get the following data from netstat and grep
>
> tcp0 0 f6be17c0fbf5:1023 f6be17c0fbf5:24007
> ESTABLISHED 31516/glusterfsd
> tcp0 0 f6be17c0fbf5:49152 f6be17c0fbf5:490
> ESTABLISHED 3151
On Jul 2, 2015, at 8:35 PM, Jeff Darcy wrote:
>> Or perhaps we could just get everyone to stop using 'inline'
>
> I agree that it would be a good thing to reduce/modify our use of
> 'inline' significantly. Any advantage gained from avoiding normal
> function-all entry/exit has to be weighed agai
Agree with Jeff
But now the question is should we have this patch go through or leave it to
float in time and space :)
http://review.gluster.org/#/c/11214/
The patch just makes the existing inline calls static or extern appropriately
without causing any harm to the existing
code but removes the
> Or perhaps we could just get everyone to stop using 'inline'
I agree that it would be a good thing to reduce/modify our use of
'inline' significantly. Any advantage gained from avoiding normal
function-all entry/exit has to be weighed against cache pollution from
having the same code repeated o
Thanks Raghavendra Talur for root causing the issue. I've reverted the patch
you pointed out.
- Original Message -
> From: "Raghavendra Talur"
> To: "Nithya Balachandran"
> Cc: "Gluster Devel"
> Sent: Thursday, July 2, 2015 6:44:22 PM
> Subject: Re: [Gluster-devel] Regression Failure:
I've reverted [1] which brought the change allow-insecure to be on by default.
The patch seems to have issues which will be addressed and merged later. The
revert can be found at [2].
[1] http://review.gluster.org/11274
[2] http://review.gluster.org/11507
Please let me know if the regressions a
I've reverted [1] which brought the change allow-insecure to be on by default.
The patch seems to have issues which will be addressed and merged later. The
revert can be found at [2].
[1] http://review.gluster.org/11274
[2] http://review.gluster.org/11507
Please let me know if the regressions a
On 07/02/2015 07:04 PM, Pranith Kumar Karampuri wrote:
hi,
When glusterfs mount process is coming up all cluster xlators wait
for at least one event from all the children before propagating the
status upwards. Sometimes client xlator takes upto 2 minutes to
propogate this
event(https://
Pranith,
I understand the bug and a more generic layer solution would be
desirable and apt, rather than repeating things at each xlator.
However, I am always confused about notifications and its processing, so
cannot state with conviction that this is fine and will work elegantly.
Will leave
Yep.. Thanks Guys.
- Original Message -
From: "Atin Mukherjee"
To: "Joseph Fernandes"
Cc: kpart...@redhat.com, "Atin Mukherjee" , "Gluster
Devel"
Sent: Thursday, July 2, 2015 9:45:01 PM
Subject: Re: [Gluster-devel] Failure in
tests/basic/tier/bug-1214222-directories_miising_after_atta
Joe,
Please refer to Prasanna's mail. He has uploaded a patch to solve it.
-Atin
Sent from one plus one
On Jul 2, 2015 9:42 PM, "Joseph Fernandes" wrote:
> Hi All,
>
> This is the same issue as the previous tiering regression failure.
>
> Volume brick not able to start brick because port is bus
Hi All,
This is the same issue as the previous tiering regression failure.
Volume brick not able to start brick because port is busy
[2015-07-02 10:20:20.601372] [run.c:190:runner_log] (-->
/build/install/lib/libglusterfs.so.0(_gf_log_callingfn+0x240)[0x7f05e080bc32]
(--> /build/install/lib/
Thanks Prasanna for the patches :)
-Atin
Sent from one plus one
On Jul 2, 2015 9:19 PM, "Prasanna Kalever" wrote:
>
> This is caused because when bind-insecure is turned on (which is the
> default now), it may happen
> that brick is not able to bind to port assigned by Glusterd for example
> 491
Not at all a problem. I am here to help Rarylson :)
-Atin
Sent from one plus one
On Jul 2, 2015 7:23 PM, "Rarylson Freitas" wrote:
> Hi Atin,
>
> You are right!!! I was using the version 3.5 in production. And when I've
> checked the Gluster source code, I checked the wrong commit (not the lates
This is caused because when bind-insecure is turned on (which is the default
now), it may happen
that brick is not able to bind to port assigned by Glusterd for example
49192-49195...
It seems to occur because the rpc_clnt connections are binding to ports in the
same range.
so brick fails to b
I agree that a generic solution for all cluster xlators would be good.
Only question I have is whether parallel notifications are specially
handled somewhere.
For example, if client xlator sends EC_CHILD_DOWN after a timeout, it's
possible that an immediate EC_CHILD_UP is sent if the brick is
Hi Atin,
You are right!!! I was using the version 3.5 in production. And when I've
checked the Gluster source code, I checked the wrong commit (not the latest
commit in the master branch).
Currently, you've already implemented my the proposed solution. It was done
at the function gd_peerinfo_find
hi,
When glusterfs mount process is coming up all cluster xlators wait
for at least one event from all the children before propagating the
status upwards. Sometimes client xlator takes upto 2 minutes to
propogate this
event(https://bugzilla.redhat.com/show_bug.cgi?id=1054694#c0) Due to
th
On Thu, Jul 2, 2015 at 4:40 PM, Raghavendra Talur <
raghavendra.ta...@gmail.com> wrote:
>
>
> On Thu, Jul 2, 2015 at 10:52 AM, Krishnan Parthasarathi <
> kpart...@redhat.com> wrote:
>
>>
>> > >
>> > > A port assigned by Glusterd for a brick is found to be in use already
>> by
>> > > the brick. Any
On Thu, Jul 2, 2015 at 1:26 PM, Nithya Balachandran
wrote:
>
>
> - Original Message -
> > From: "Kotresh Hiremath Ravishankar"
> > To: "Susant Palai"
> > Cc: "Gluster Devel"
> > Sent: Thursday, July 2, 2015 1:03:18 PM
> > Subject: Re: [Gluster-devel] Regression Failure: ./tests/basic/q
Thanks Dan!.
Pranith
On 07/02/2015 06:14 PM, Dan Lambright wrote:
I'll check on this.
- Original Message -
From: "Pranith Kumar Karampuri"
To: "Gluster Devel" , "Joseph Fernandes"
Sent: Thursday, July 2, 2015 5:40:34 AM
Subject: [Gluster-devel] Failure in
tests/basic/tier/bug-
I'll check on this.
- Original Message -
> From: "Pranith Kumar Karampuri"
> To: "Gluster Devel" , "Joseph Fernandes"
>
> Sent: Thursday, July 2, 2015 5:40:34 AM
> Subject: [Gluster-devel] Failure in
> tests/basic/tier/bug-1214222-directories_miising_after_attach_tier.t
>
> hi Josep
hi Joseph,
Could you take a look at
http://build.gluster.org/job/rackspace-regression-2GB-triggered/11842/consoleFull
Pranith
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel
On Thu, Jul 2, 2015 at 10:52 AM, Krishnan Parthasarathi wrote:
>
> > >
> > > A port assigned by Glusterd for a brick is found to be in use already
> by
> > > the brick. Any changes in Glusterd recently which can cause this?
> > >
> > > Or is it a test infra problem?
>
> This issue is likely to be
Hi,
glusterfs-3.6.4beta1 has been released and the packages for
RHEL/Fedora/Centos can be found here.
http://download.gluster.org/pub/gluster/glusterfs/qa-releases/3.6.4beta2/
Requesting people running 3.6.x to please try it out and let us know if
there are any issues.
This release supposed
- Original Message -
> From: "Kotresh Hiremath Ravishankar"
> To: "Susant Palai"
> Cc: "Gluster Devel"
> Sent: Thursday, July 2, 2015 1:03:18 PM
> Subject: Re: [Gluster-devel] Regression Failure: ./tests/basic/quota.t
>
> Comments inline.
>
> Thanks and Regards,
> Kotresh H R
>
> --
Working fine for me now. In case someone hasn't checked, try using it.
- Original Message -
> From: "Anoop C S"
> To: gluster-devel@gluster.org
> Cc: "Anuradha Talur"
> Sent: Thursday, July 2, 2015 10:41:35 AM
> Subject: Re: [Gluster-devel] Unable to send patches to review.gluster.org
>
Comments inline.
Thanks and Regards,
Kotresh H R
- Original Message -
> From: "Susant Palai"
> To: "Sachin Pandit"
> Cc: "Kotresh Hiremath Ravishankar" , "Gluster Devel"
>
> Sent: Thursday, July 2, 2015 12:35:08 PM
> Subject: Re: [Gluster-devel] Regression Failure: ./tests/basic/quota
Comments inline.
- Original Message -
> From: "Sachin Pandit"
> To: "Kotresh Hiremath Ravishankar"
> Cc: "Gluster Devel"
> Sent: Thursday, July 2, 2015 12:21:44 PM
> Subject: Re: [Gluster-devel] Regression Failure: ./tests/basic/quota.t
>
> - Original Message -
> > From: "Vijai
31 matches
Mail list logo
