Unfortunately, there is no recording. However, we are willing to discuss
our findings if you've specific questions. We can do that in this thread.
On Thu, Mar 7, 2019 at 10:33 AM Strahil wrote:
> Thanks a lot.
> Is there a recording of that ?
>
> Best Regards,
> Strahil Nikolov
> On Mar 5, 2019
No, it is not necessary that the first brick would be local one.
I really don't think starting from local node will make a difference.
The major time spent is not in getting list of entries from
.gluster/indices/xattrop folder.
The LOCK->XATTR_CHECK->UNLOCK is the cycle which takes most of
Le mercredi 06 mars 2019 à 17:53 +0530, Sankarshan Mukhopadhyay a
écrit :
> On Wed, Mar 6, 2019 at 5:38 PM Deepshikha Khandelwal
> wrote:
> >
> > Hello,
> >
> > Today while debugging the centos7-regression failed builds I saw
> > most of the builders did not pass the instance status check on
Yes, Mohit is looking into it. There's some issue in the patch itself.
I forgot to link the bug filed for this:
https://bugzilla.redhat.com/show_bug.cgi?id=1685813
On Wed, Mar 6, 2019 at 5:54 PM Sankarshan Mukhopadhyay <
sankarshan.mukhopadh...@gmail.com> wrote:
> On Wed, Mar 6, 2019 at 5:38 PM
On Wed, Mar 6, 2019 at 5:38 PM Deepshikha Khandelwal
wrote:
>
> Hello,
>
> Today while debugging the centos7-regression failed builds I saw most of the
> builders did not pass the instance status check on AWS and were unreachable.
>
> Misc investigated this and came to know about the patch[1]
Hello,
Today while debugging the centos7-regression failed builds I saw most of
the builders did not pass the instance status check on AWS and were
unreachable.
Misc investigated this and came to know about the patch[1] which seems to
break the builder one after the other. They all ran the
Hi Abhishek,
Good to know that you have resolved your problem. Do you think any more
information is required to add in the upgrade doc for a smooth upgrade
flow. It would be great to see a PR to the repo
https://github.com/gluster/glusterdocs/tree/master/docs/Upgrade-Guide
for updating the
Hi Sanju,
Thanks for the response.
I have resolved the issue, actually I have updated from 3.7.6 to 5.0, in
new version RPC is coming from libtirpb , but I forgot to enable
"--with-libtirpc" in configuration.
After enabling able to start glusterd.
Regards,
Abhishek
On Wed, Mar 6, 2019 at
