[Gluster-devel] Minutes of Gluster Community Bug Triage meeting at 12:00 UTC ~(in 1.5 hours)

[Jiffin Tony Thottan]

 Meeting summary

1. *Roll call* (jiffin
   
,
   12:01:29)
2. *msvbhat will look into lalatenduM's automated Coverity setup in
   Jenkins which need assistance from an admin with more permissions*
   (jiffin
   
,
   12:05:12)
1. /ACTION/: kkeithley Saravanakmr will set up Coverity, clang, etc
   on public facing machine and run it regularly (jiffin
   
,
   12:12:44)
2. http://download.gluster.org/pub/gluster/glusterfs/static-analysis/
   (jiffin
   
,
   12:13:30)
3. /ACTION/: ndevos need to decide on how to provide/use debug
   builds (jiffin
   
,
   12:17:26)
4. /ACTION/: ndevos to propose some test-cases for minimal libgfapi
   test (jiffin
   
,
   12:17:37)

3. *Manikandan and gem to followup with kshlm to get access to
   gluster-infra* (jiffin
   
,
   12:17:59)
1. /ACTION/: Manikandan and gem to followup with kshlm/misc to get
   access to gluster-infra (jiffin
   
,
   12:20:41)

4. *Group Triage* (jiffin
   
,
   12:22:22)
1. https://public.pad.fsfe.org/p/gluster-bugs-to-triage (jiffin
   
,
   12:22:41)

5. *Get moderators for June 2016* (jiffin
   
,
   12:37:34)
1. /ACTION/: Saravanakmr will host bug triage meeting on June 14th
   2016 (jiffin
   
,
   12:40:20)
2. /ACTION/: Manikandan will host bug triage meeting on June 21st
   2016 (jiffin
   
,
   12:41:31)
3. /ACTION/: ndevos will host bug triage meeting on June 28th 2016
   (jiffin
   
,
   12:42:54)
4. /ACTION/: Jiffin will host bug triage meeting on June 7th 2016
   (jiffin
   
,
   12:44:09)

6. *Open Floror* (jiffin
   
,
   12:44:43)
7. *Open Floor* (jiffin
   
,
   12:45:07)
1. /ACTION/: ? decide how component maintainers/developers use the
   BZ queries or RSS-feeds for the Triaged bugs (jiffin
   
,
   13:00:52)



Meeting ended at 13:02:21 UTC (full logs 
). 




 Action items

1. kkeithley Saravanakmr will set up Coverity, clang, etc on public
   facing machine and run it regularly
2. ndevos need to decide on how to provide/use debug builds
3. ndevos to propose some test-cases for minimal libgfapi test
4. Manikandan and gem to followup with kshlm/misc to get access to
   gluster-infra
5. Saravanakmr will host bug triage meeting on June 14th 2016
6. Manikandan will host bug triage meeting on June 21st 2016
7. ndevos will host bug triage meeting on June 28th 2016
8. Jiffin will host bug triage meeting on June 7th 2016
9. ? decide how component maintainers/developers use the BZ queries or
   RSS-feeds for the Triaged bugs



 Action items, by person

1. kkeithley
1. kkeithley Saravanakmr will set up Coverity, clang, etc on public
   facing machine and run it regularly
2. Manikandan
1. Manikandan and gem to followup with kshlm/misc to get access

[Gluster-devel] REMINDER: Weekly Gluster Community meeting starts in ~15mnts

[Mohammed Rafi K C]

Hi all,

The weekly Gluster community meeting is starting in 1 hour at 12:00 UTC.
The current agenda for the meeting is below. Add any further topics to
the agenda at https://public.pad.fsfe.org/p/gluster-community-meetings

Meeting details:
- location: #gluster-meeting on Freenode IRC
- date: every Wednesday
- time: 8:00 EDT, 12:00 UTC, 13:00 CET, 17:30 IST
(in your terminal, run: date -d "12:00 UTC")

Current Agenda:
 * Roll Call
 * AIs from last meeting
 * GlusterFS 3.7
 * GlusterFS 3.6
 * GlusterFS 3.5
 * GlusterFS 3.8
 * GlusterFS 3.9
 * GlusterFS 4.0
 * Open Floor

See you there,
Rafi



___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

[Gluster-devel] Issues from Gerrit Upgrade

[Nigel Babu]

Hello folks,

This upgrade has produced a side effect.

*What Does Not Work*:
Some people cannot login to Gerrit's web interface

*What Does Work*:
You can continue to push code and open review requests.

*Problem*:
If you have different github account and different gerrit username, you
can't login to gerrit. For example, if your github username is nigelbabu
and your gerrit username is nigelb, you can't login.

*Affected*:
People with a github account different from their gerrit username.

*Solutions*:
There are multiple solutions here and I'm yet to figure out which one I'll
go with. In the meanwhile, I'd like a list of people affected, while I work
out how to fix this. Please add your Gerrit username and Github username
onto this etherpad if you're affected by this issue.

https://public.pad.fsfe.org/p/gluster-login-issues

If your gerrit username is the same as your github username, you should be
able to login without any issues. Please ignore the actions in this email.

*Future Actions*:
* We'll make it clear in the onboading process that having your github
username same as your gerrit username is compulsory. By the way this plugin
works, I think it will enforce it anyway.
* Better QA of a new version of Gerrit in staging before we upgrade. I
skipped ahead with the upgrade a little too quickly. This would have
otherwise been caught.


On Wed, Jun 1, 2016 at 3:30 PM, Atin Mukherjee  wrote:

>
>
> On 06/01/2016 08:40 AM, Nigel Babu wrote:
> > Hello folks,
> >
> > The upgrade is now complete! Please let me know if you notice anything
> > wrong.
>
> It does appear slow to me compared to previous version.
>
> >
> > On Wed, Jun 1, 2016 at 7:45 AM, Nigel Babu  > > wrote:
> >
> > Hello,
> >
> > I'll be bring down Gerrit for upgrade to the latest version. I'll
> > update this thread when the upgrade is completed.
> >
> > --
> > nigelb
> >
> >
> >
> >
> > --
> > nigelb
> >
> >
> > ___
> > Gluster-devel mailing list
> > Gluster-devel@gluster.org
> > http://www.gluster.org/mailman/listinfo/gluster-devel
> >
>



-- 
nigelb
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Gerrit (review.gluster.org/git.gluster.org) downtime in 15 mins

[Atin Mukherjee]

On 06/01/2016 08:40 AM, Nigel Babu wrote:
> Hello folks,
> 
> The upgrade is now complete! Please let me know if you notice anything
> wrong.

It does appear slow to me compared to previous version.

> 
> On Wed, Jun 1, 2016 at 7:45 AM, Nigel Babu  > wrote:
> 
> Hello,
> 
> I'll be bring down Gerrit for upgrade to the latest version. I'll
> update this thread when the upgrade is completed.
> 
> -- 
> nigelb
> 
> 
> 
> 
> -- 
> nigelb
> 
> 
> ___
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-devel
> 
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Gerrit (review.gluster.org/git.gluster.org) downtime in 15 mins

[Nigel Babu]

I'm looking into this now.

On Wed, Jun 1, 2016 at 11:58 AM, Susant Palai  wrote:

> Getting "server error" while trying to login.
>
> Regards,
> Susant
>
> - Original Message -
> From: "Nigel Babu" 
> To: "gluster-devel" , "gluster-infra" <
> gluster-in...@gluster.org>
> Sent: Wednesday, 1 June, 2016 8:40:27 AM
> Subject: Re: [Gluster-devel] Gerrit (review.gluster.org/git.gluster.org)
>   downtime in 15 mins
>
>
>
>
> Hello folks,
>
> The upgrade is now complete! Please let me know if you notice anything
> wrong.
>
>
>
> On Wed, Jun 1, 2016 at 7:45 AM, Nigel Babu < nig...@redhat.com > wrote:
>
>
>
>
> Hello,
>
> I'll be bring down Gerrit for upgrade to the latest version. I'll update
> this thread when the upgrade is completed.
>
>
>
>
> --
>
>
> nigelb
>
>
>
> --
>
>
> nigelb
>
> ___
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-devel
>



-- 
nigelb
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] dht mkdir preop check, afr and (non-)readable afr subvols

[Xavier Hernandez]

Hi,

On 01/06/16 08:53, Raghavendra Gowdappa wrote:



- Original Message -

From: "Xavier Hernandez" 
To: "Pranith Kumar Karampuri" , "Raghavendra G" 

Cc: "Gluster Devel" 
Sent: Wednesday, June 1, 2016 11:57:12 AM
Subject: Re: [Gluster-devel] dht mkdir preop check, afr and (non-)readable afr 
subvols

Oops, you are right. For entry operations the current version of the
parent directory is not checked, just to avoid this problem.

This means that mkdir will be sent to all alive subvolumes. However it
still selects the group of answers that have a minimum quorum equal or
greater than #bricks - redundancy. So it should be still valid.


What if the quorum is met on "bad" subvolumes? and mkdir was successful on bad 
subvolumes? Do we consider mkdir as successful? If yes, even EC suffers from the problem 
described in bz https://bugzilla.redhat.com/show_bug.cgi?id=1341429.


I don't understand the real problem. How a subvolume of EC could be in 
bad state from the point of view of DHT ?


If you use xattrs to configure something in the parent directories, you 
should have needed to use setxattr or xattrop to do that. These 
operations do consider good/bad bricks because they touch inode 
metadata. This will only succeed if enough (quorum) bricks have 
successfully processed it. If quorum is met but for an error answer, an 
error will be reported to DHT and the majority of bricks will be left in 
the old state (these should be considered the good subvolumes). If some 
brick has succeeded, it will be considered bad and will be healed. If no 
quorum is met (even for an error answer), EIO will be returned and the 
state of the directory should be considered unknown/damaged.


If a later mkdir checks this value in storage/posix and succeeds in 
enough bricks, it necessarily means that is has succeeded in good 
bricks, because there cannot be enough bricks with the bad xattr value.


Note that quorum is always > #bricks/2 so we cannot have a quorum with 
good and bad bricks at the same time.


Xavi





Xavi

On 01/06/16 06:51, Pranith Kumar Karampuri wrote:

Xavi,
But if we keep winding only to good subvolumes, there is a case
where bad subvolumes will never catch up right? i.e. if we keep creating
files in same directory and everytime self-heal completes there are more
entries mounts would have created on the good subvolumes alone. I think
I must have missed this in the reviews if this is the current behavior.
It was not in the earlier releases. Right?

Pranith

On Tue, May 31, 2016 at 2:17 PM, Raghavendra G mailto:raghaven...@gluster.com>> wrote:



On Tue, May 31, 2016 at 12:37 PM, Xavier Hernandez
mailto:xhernan...@datalab.es>> wrote:

Hi,

On 31/05/16 07:05, Raghavendra Gowdappa wrote:

+gluster-devel, +Xavi

Hi all,

The context is [1], where bricks do pre-operation checks
before doing a fop and proceed with fop only if pre-op check
is successful.

@Xavi,

We need your inputs on behavior of EC subvolumes as well.


If I understand correctly, EC shouldn't have any problems here.

EC sends the mkdir request to all subvolumes that are currently
considered "good" and tries to combine the answers. Answers that
match in return code, errno (if necessary) and xdata contents
(except for some special xattrs that are ignored for combination
purposes), are grouped.

Then it takes the group with more members/answers. If that group
has a minimum size of #bricks - redundancy, it is considered the
good answer. Otherwise EIO is returned because bricks are in an
inconsistent state.

If there's any answer in another group, it's considered bad and
gets marked so that self-heal will repair it using the good
information from the majority of bricks.

xdata is combined and returned even if return code is -1.

Is that enough to cover the needed behavior ?


Thanks Xavi. That's sufficient for the feature in question. One of
the main cases I was interested in was what would be the behaviour
if mkdir succeeds on "bad" subvolume and fails on "good" subvolume.
Since you never wind mkdir to "bad" subvolume(s), this situation
never arises.




Xavi



[1] http://review.gluster.org/13885

regards,
Raghavendra

- Original Message -

From: "Pranith Kumar Karampuri" mailto:pkara...@redhat.com>>
To: "Raghavendra Gowdappa" mailto:rgowd...@redhat.com>>
Cc: "team-quine-afr" mailto:team-quine-...@redhat.com>>, "rhs-zteam"
mailto:rhs-zt...@redhat.com>>
Sent: Tuesday, May 31, 2016 10:22:49 AM
Subject: Re: dht mkdir preop check, afr and
(non-)readable afr subvols

I think you should start a discussion o