[Gluster-devel] Be careful before closing fd in a default case

2019-04-11 Thread Mohit Agrawal
Hi, I want to highlight recent bug( https://bugzilla.redhat.com/show_bug.cgi?id=1699025) due to raised after fixed one Coverity bug https://review.gluster.org/#/c/glusterfs/+/20720/ As we know all gluster processes initially keeping open standard fd's (0,1,2) at the time of daemonizing so

Re: [Gluster-devel] test failure reports for last 15 days

2019-04-11 Thread FNU Raghavendra Manjunath
While analysing the logs of the runs where uss.t failed made following observations. 1) In the first iteration of uss.t, the time difference between the first test of the .t file and the last test of the .t file is just within 1 minute. But, I think it is the cleanup sequence which is taking

[Gluster-devel] [Gluster-infra] Upgrading build.gluster.org

2019-04-11 Thread Deepshikha Khandelwal
Hello, I’ve planned to do an upgrade of build.gluster.org tomorrow morning so as to install and pull in the latest security upgrade of the Jenkins plugins. I’ll stop all the running jobs and re-trigger them once I'm done with the upgrade. The downtime window will be from : UTC: 0330 to 0400 IST:

Re: [Gluster-devel] [Gluster-users] Replica 3 - how to replace failed node (peer)

2019-04-11 Thread Karthik Subrahmanya
On Thu, Apr 11, 2019 at 1:40 PM Strahil Nikolov wrote: > Hi Karthik, > > - the volume configuration you were using? > I used oVirt 4.2.6 Gluster Wizard, so I guess - we need to involve the > oVirt devs here. > - why you wanted to replace your brick? > I have deployed the arbiter on another

Re: [Gluster-devel] [Gluster-users] Replica 3 - how to replace failed node (peer)

2019-04-11 Thread Karthik Subrahmanya
On Thu, Apr 11, 2019 at 12:43 PM Martin Toth wrote: > Hi Karthik, > > more over, I would like to ask if there are some recommended > settings/parameters for SHD in order to achieve good or fair I/O while > volume will be healed when I will replace Brick (this should trigger > healing process). >

Re: [Gluster-devel] test failure reports for last 15 days

2019-04-11 Thread Xavi Hernandez
On Thu, Apr 11, 2019 at 11:28 AM Xavi Hernandez wrote: > On Wed, Apr 10, 2019 at 7:25 PM Xavi Hernandez > wrote: > >> On Wed, Apr 10, 2019 at 4:01 PM Atin Mukherjee >> wrote: >> >>> And now for last 15 days: >>> >>> >>> https://fstat.gluster.org/summary?start_date=2019-03-25_date=2019-04-10

Re: [Gluster-devel] test failure reports for last 15 days

2019-04-11 Thread Xavi Hernandez
On Wed, Apr 10, 2019 at 7:25 PM Xavi Hernandez wrote: > On Wed, Apr 10, 2019 at 4:01 PM Atin Mukherjee > wrote: > >> And now for last 15 days: >> >> >> https://fstat.gluster.org/summary?start_date=2019-03-25_date=2019-04-10 >> >> ./tests/bitrot/bug-1373520.t 18 ==> Fixed through >>

[Gluster-devel] Invitation: Gluster Community Meeting (NA/EMEA friendly hours) @ Tue Apr 23, 2019 10:30pm - 11:30pm (IST) (gluster-devel@gluster.org)

2019-04-11 Thread amarts
BEGIN:VCALENDAR PRODID:-//Google Inc//Google Calendar 70.9054//EN VERSION:2.0 CALSCALE:GREGORIAN METHOD:REQUEST BEGIN:VEVENT DTSTART:20190423T17Z DTEND:20190423T18Z DTSTAMP:20190411T085751Z ORGANIZER;CN=Gluster Community Calendar:mailto:vebj5bl0knsb9d0cm9eh9pbli4@g

[Gluster-devel] Invitation: Gluster Community Meeting (APAC friendly hours) @ Tue Apr 16, 2019 11:30am - 12:30pm (IST) (gluster-devel@gluster.org)

2019-04-11 Thread amarts
BEGIN:VCALENDAR PRODID:-//Google Inc//Google Calendar 70.9054//EN VERSION:2.0 CALSCALE:GREGORIAN METHOD:REQUEST BEGIN:VEVENT DTSTART:20190416T06Z DTEND:20190416T07Z DTSTAMP:20190411T085648Z ORGANIZER;CN=Gluster Community Calendar:mailto:vebj5bl0knsb9d0cm9eh9pbli4@g

Re: [Gluster-devel] [Gluster-users] Proposal: Changes in Gluster Community meetings

2019-04-11 Thread Amar Tumballi Suryanarayan
Hi All, Below is the final details of our community meeting, and I will be sending invites to mailing list following this email. You can add Gluster Community Calendar so you can get notifications on the meetings. We are starting the meetings from next week. For the first meeting, we need 1

[Gluster-devel] Unplanned Jenkins restart

2019-04-11 Thread Deepshikha Khandelwal
Hello, I had to do an unplanned Jenkins restart. Jenkins was not responding to any of the requests and was not giving back the regression votes. I did update the vote verified values of regression jobs which seemed to change to 0 all of a sudden and was not giving back the vote. I'm investigating