Re: [Gluster-Maintainers] Release 5: GA and what are we waiting on

[Raghavendra Gowdappa]

On Thu, Oct 11, 2018 at 9:16 PM Krutika Dhananjay 
wrote:

>
>
> On Thu, Oct 11, 2018 at 8:55 PM Shyam Ranganathan 
> wrote:
>
>> So we are through with a series of checks and tasks on release-5 (like
>> ensuring all backports to other branches are present in 5, upgrade
>> testing, basic performance testing, Package testing, etc.), but still
>> need the following resolved else we stand to delay the release GA
>> tagging, which I hope to get done over the weekend or by Monday 15th
>> morning (EDT).
>>
>> 1) Fix for libgfapi-python related blocker on Gluster:
>> https://bugzilla.redhat.com/show_bug.cgi?id=1630804
>
>
I'll take a look and respond over the bz.


>
>>
>> @ppai, who needs to look into this?
>>
>> 2) Release notes for options added to the code (see:
>> https://lists.gluster.org/pipermail/gluster-devel/2018-October/055563.html
>> )
>>
>> @du, @krutika can we get some text for the options referred in the mail
>> above?
>>
>
I just responded in the other thread.


>
>>
> Replied here -
> https://lists.gluster.org/pipermail/gluster-devel/2018-October/055577.html
>
> -Krutika
>
> 3) Python3 testing
>> - Heard back from Kotresh on geo-rep passing and saw that we have
>> handled cliutils issues
>> - Anything more to cover? (@aravinda, @kotresh, @ppai?)
>> - We are attempting to get a regression run on a Python3 platform, but
>> that maybe a little ways away from the release (see:
>> https://bugzilla.redhat.com/show_bug.cgi?id=1638030 )
>>
>> Request attention to the above, to ensure we are not breaking things
>> with the release.
>>
>> Thanks,
>> Shyam
>>
>
___
maintainers mailing list
maintainers@gluster.org
https://lists.gluster.org/mailman/listinfo/maintainers

Re: [Gluster-Maintainers] Release 5: Missing option documentation (need inputs)

[Raghavendra Gowdappa]

On Wed, Oct 10, 2018 at 8:30 PM Shyam Ranganathan 
wrote:

> The following options were added post 4.1 and are part of 5.0 as the
> first release for the same. They were added in as part of bugs, and
> hence looking at github issues to track them as enhancements did not
> catch the same.
>
> We need to document it in the release notes (and also the gluster doc.
> site ideally), and hence I would like a some details on what to write
> for the same (or release notes commits) for them.
>
> Option: cluster.daemon-log-level
> Attention: @atin
> Review: https://review.gluster.org/c/glusterfs/+/20442
>
> Option: ctime-invalidation
> Attention: @Du
> Review: https://review.gluster.org/c/glusterfs/+/20286


Quick-read by default uses mtime to identify changes to file data. However
there are applications like rsync which explicitly set mtime making it
unreliable for the purpose of identifying change in file content. Since
ctime also changes when content of a file changes and it cannot be set
explicitly, it becomes suitable for identifying staleness of cached data.
This option makes quick-read to prefer ctime over mtime to validate its
cache. However, using ctime can result in false positives as ctime changes
with just attribute changes like permission without changes to file data.
So, use this option only when mtime is not reliable.


>
> Option: shard-lru-limit
> Attention: @krutika
> Review: https://review.gluster.org/c/glusterfs/+/20544
>
> Option: shard-deletion-rate
> Attention: @krutika
> Review: https://review.gluster.org/c/glusterfs/+/19970
>
> Please send in the required text ASAP, as we are almost towards the end
> of the release.
>
> Thanks,
> Shyam
>
___
maintainers mailing list
maintainers@gluster.org
https://lists.gluster.org/mailman/listinfo/maintainers

[Gluster-Maintainers] Jenkins build is back to normal : regression-test-with-multiplex #904

[jenkins]

See 


___
maintainers mailing list
maintainers@gluster.org
https://lists.gluster.org/mailman/listinfo/maintainers

Re: [Gluster-Maintainers] [Gluster-devel] Release 5: GA and what are we waiting on

[Shyam Ranganathan]

On 10/11/2018 11:25 AM, Shyam Ranganathan wrote:
> 1) Fix for libgfapi-python related blocker on Gluster:
> https://bugzilla.redhat.com/show_bug.cgi?id=1630804


@du @krutika, the root cause for the above issue is from the commit,

commit c9bde3021202f1d5c5a2d19ac05a510fc1f788ac
https://review.gluster.org/c/glusterfs/+/20639

performance/readdir-ahead: keep stats of cached dentries in sync with
modifications

I have updated the bug with the required findings, please take a look
and let us know if we can get a fix in time for release-5.

Thanks,
Shyam
___
maintainers mailing list
maintainers@gluster.org
https://lists.gluster.org/mailman/listinfo/maintainers

[Gluster-Maintainers] Build failed in Jenkins: regression-test-with-multiplex #903

[jenkins]

See 


Changes:

[Amar Tumballi] cluster/dht : Fix coverity issue

[Amar Tumballi] README: add a section for giving hints on testing

[Raghavendra G] socket: set FD_CLOEXEC on all sockets

--
[...truncated 1010.62 KB...]
./tests/bugs/posix/bug-1360679.t  -  9 second
./tests/bugs/md-cache/bug-1211863.t  -  9 second
./tests/bugs/glusterfs-server/bug-904300.t  -  9 second
./tests/bugs/glusterfs/bug-872923.t  -  9 second
./tests/bugs/changelog/bug-1208470.t  -  9 second
./tests/bugs/bitrot/1209751-bitrot-scrub-tunable-reset.t  -  9 second
./tests/basic/quota-nfs.t  -  9 second
./tests/basic/glusterd/arbiter-volume-probe.t  -  9 second
./tests/basic/gfapi/mandatory-lock-optimal.t  -  9 second
./tests/basic/fop-sampling.t  -  9 second
./tests/basic/ec/ec-anonymous-fd.t  -  9 second
./tests/basic/distribute/file-create.t  -  9 second
./tests/basic/afr/arbiter-statfs.t  -  9 second
./tests/gfid2path/get-gfid-to-path.t  -  8 second
./tests/features/lock-migration/lkmigration-set-option.t  -  8 second
./tests/bugs/upcall/bug-1458127.t  -  8 second
./tests/bugs/upcall/bug-1227204.t  -  8 second
./tests/bugs/shard/bug-1488546.t  -  8 second
./tests/bugs/quota/bug-1250582-volume-reset-should-not-remove-quota-quota-deem-statfs.t
  -  8 second
./tests/bugs/quota/bug-1243798.t  -  8 second
./tests/bugs/io-stats/bug-1598548.t  -  8 second
./tests/bugs/io-cache/bug-858242.t  -  8 second
./tests/bugs/glusterfs/bug-893338.t  -  8 second
./tests/bugs/gfapi/bug-1447266/1460514.t  -  8 second
./tests/bugs/fuse/bug-985074.t  -  8 second
./tests/bugs/fuse/bug-963678.t  -  8 second
./tests/bugs/ec/bug-1179050.t  -  8 second
./tests/bugs/cli/bug-1087487.t  -  8 second
./tests/bugs/bitrot/bug-1229134-bitd-not-support-vol-set.t  -  8 second
./tests/bugs/bitrot/1209818-vol-info-show-scrub-process-properly.t  -  8 second
./tests/bugs/bitrot/1207029-bitrot-daemon-should-start-on-valid-node.t  -  8 
second
./tests/bitrot/br-stub.t  -  8 second
./tests/basic/xlator-pass-through-sanity.t  -  8 second
./tests/basic/volume-status.t  -  8 second
./tests/basic/ec/ec-read-policy.t  -  8 second
./tests/basic/ctime/ctime-noatime.t  -  8 second
./tests/basic/afr/ta-shd.t  -  8 second
./tests/basic/afr/gfid-mismatch.t  -  8 second
./tests/basic/afr/arbiter-remove-brick.t  -  8 second
./tests/gfid2path/block-mount-access.t  -  7 second
./tests/bugs/snapshot/bug-1260848.t  -  7 second
./tests/bugs/snapshot/bug-1064768.t  -  7 second
./tests/bugs/shard/bug-1258334.t  -  7 second
./tests/bugs/replicate/bug-1365455.t  -  7 second
./tests/bugs/quota/bug-1104692.t  -  7 second
./tests/bugs/nfs/bug-915280.t  -  7 second
./tests/bugs/nfs/bug-1143880-fix-gNFSd-auth-crash.t  -  7 second
./tests/bugs/nfs/bug-1116503.t  -  7 second
./tests/bugs/io-cache/bug-read-hang.t  -  7 second
./tests/bugs/glusterfs/bug-861015-log.t  -  7 second
./tests/bugs/glusterfs/bug-848251.t  -  7 second
./tests/bugs/ec/bug-1227869.t  -  7 second
./tests/bugs/distribute/bug-882278.t  -  7 second
./tests/bugs/distribute/bug-1088231.t  -  7 second
./tests/bugs/core/bug-986429.t  -  7 second
./tests/bugs/core/bug-908146.t  -  7 second
./tests/bugs/cli/bug-982174.t  -  7 second
./tests/bugs/cli/bug-1022905.t  -  7 second
./tests/bitrot/bug-1221914.t  -  7 second
./tests/basic/gfapi/upcall-cache-invalidate.t  -  7 second
./tests/basic/gfapi/glfd-lkowner.t  -  7 second
./tests/basic/gfapi/gfapi-dup.t  -  7 second
./tests/basic/gfapi/bug-1241104.t  -  7 second
./tests/basic/gfapi/anonymous_fd.t  -  7 second
./tests/basic/ec/nfs.t  -  7 second
./tests/basic/ec/ec-internal-xattrs.t  -  7 second
./tests/basic/ec/dht-rename.t  -  7 second
./tests/basic/ctime/ctime-glfs-init.t  -  7 second
./tests/basic/changelog/changelog-rename.t  -  7 second
./tests/basic/afr/tarissue.t  -  7 second
./tests/basic/afr/heal-info.t  -  7 second
./tests/basic/afr/gfid-heal.t  -  7 second
./tests/basic/afr/afr-read-hash-mode.t  -  7 second
./tests/features/readdir-ahead.t  -  6 second
./tests/bugs/upcall/bug-upcall-stat.t  -  6 second
./tests/bugs/upcall/bug-1369430.t  -  6 second
./tests/bugs/transport/bug-873367.t  -  6 second
./tests/bugs/shard/bug-1272986.t  -  6 second
./tests/bugs/shard/bug-1259651.t  -  6 second
./tests/bugs/replicate/bug-767585-gfid.t  -  6 second
./tests/bugs/replicate/bug-1250170-fsync.t  -  6 second
./tests/bugs/replicate/bug-1101647.t  -  6 second
./tests/bugs/quota/bug-1287996.t  -  6 second
./tests/bugs/nfs/zero-atime.t  -  6 second
./tests/bugs/nfs/bug-877885.t  -  6 second
./tests/bugs/nfs/bug-847622.t  -  6 second
./tests/bugs/nfs/bug-1210338.t  -  6 second
./tests/bugs/glusterfs-server/bug-873549.t  -  6 second
./tests/bugs/glusterfs-server/bug-864222.t  -  6 second
./tests/bugs/glusterfs/bug-902610.t  -  6 second
./tests/bugs/glusterfs/bug-893378.t  -  6 second
./tests/bugs/glusterd/bug-948729/bug-948729-mode-script.t  -  6 second

Re: [Gluster-Maintainers] Release 5: GA and what are we waiting on

[Krutika Dhananjay]

On Thu, Oct 11, 2018 at 8:55 PM Shyam Ranganathan 
wrote:

> So we are through with a series of checks and tasks on release-5 (like
> ensuring all backports to other branches are present in 5, upgrade
> testing, basic performance testing, Package testing, etc.), but still
> need the following resolved else we stand to delay the release GA
> tagging, which I hope to get done over the weekend or by Monday 15th
> morning (EDT).
>
> 1) Fix for libgfapi-python related blocker on Gluster:
> https://bugzilla.redhat.com/show_bug.cgi?id=1630804
>
> @ppai, who needs to look into this?
>
> 2) Release notes for options added to the code (see:
> https://lists.gluster.org/pipermail/gluster-devel/2018-October/055563.html
> )
>
> @du, @krutika can we get some text for the options referred in the mail
> above?
>
>
Replied here -
https://lists.gluster.org/pipermail/gluster-devel/2018-October/055577.html

-Krutika

3) Python3 testing
> - Heard back from Kotresh on geo-rep passing and saw that we have
> handled cliutils issues
> - Anything more to cover? (@aravinda, @kotresh, @ppai?)
> - We are attempting to get a regression run on a Python3 platform, but
> that maybe a little ways away from the release (see:
> https://bugzilla.redhat.com/show_bug.cgi?id=1638030 )
>
> Request attention to the above, to ensure we are not breaking things
> with the release.
>
> Thanks,
> Shyam
>
___
maintainers mailing list
maintainers@gluster.org
https://lists.gluster.org/mailman/listinfo/maintainers

Re: [Gluster-Maintainers] Release 5: Missing option documentation (need inputs)

[Krutika Dhananjay]

On Wed, Oct 10, 2018 at 8:30 PM Shyam Ranganathan 
wrote:

> The following options were added post 4.1 and are part of 5.0 as the
> first release for the same. They were added in as part of bugs, and
> hence looking at github issues to track them as enhancements did not
> catch the same.
>
> We need to document it in the release notes (and also the gluster doc.
> site ideally), and hence I would like a some details on what to write
> for the same (or release notes commits) for them.
>
> Option: cluster.daemon-log-level
> Attention: @atin
> Review: https://review.gluster.org/c/glusterfs/+/20442
>
> Option: ctime-invalidation
> Attention: @Du
> Review: https://review.gluster.org/c/glusterfs/+/20286
>
> Option: shard-lru-limit
> Attention: @krutika
> Review: https://review.gluster.org/c/glusterfs/+/20544


I added this option solely to make it easier to hit shard's in-memory lru
limit and enable testing of different cases that arise when the limit is
reached.
For this reason, this option is also marked "NO_DOC" in the code. So we
don't need to document it in the release notes.


>
> Option: shard-deletion-rate
> Attention: @krutika
> Review: https://review.gluster.org/c/glusterfs/+/19970
>
> Please send in the required text ASAP, as we are almost towards the end
>
of the release.
>

This option is used to configure the number of shards to delete in parallel
when the original file is deleted. The default value is 100. But it can
always be increased to delete more shards in parallel for faster freeing up
of space. The upper limit is yet to be fixed.  But use it with caution as a
very large number will cause serious lock contention issues on the bricks
(in locks translator). As an example, in our testing, an upper limit of
125000 was enough to cause timeouts and hangs in the gluster processes due
to lock contention.

-Krutika


> Thanks,
> Shyam
>
___
maintainers mailing list
maintainers@gluster.org
https://lists.gluster.org/mailman/listinfo/maintainers

[Gluster-Maintainers] Release 5: GA and what are we waiting on

[Shyam Ranganathan]

So we are through with a series of checks and tasks on release-5 (like
ensuring all backports to other branches are present in 5, upgrade
testing, basic performance testing, Package testing, etc.), but still
need the following resolved else we stand to delay the release GA
tagging, which I hope to get done over the weekend or by Monday 15th
morning (EDT).

1) Fix for libgfapi-python related blocker on Gluster:
https://bugzilla.redhat.com/show_bug.cgi?id=1630804

@ppai, who needs to look into this?

2) Release notes for options added to the code (see:
https://lists.gluster.org/pipermail/gluster-devel/2018-October/055563.html )

@du, @krutika can we get some text for the options referred in the mail
above?

3) Python3 testing
- Heard back from Kotresh on geo-rep passing and saw that we have
handled cliutils issues
- Anything more to cover? (@aravinda, @kotresh, @ppai?)
- We are attempting to get a regression run on a Python3 platform, but
that maybe a little ways away from the release (see:
https://bugzilla.redhat.com/show_bug.cgi?id=1638030 )

Request attention to the above, to ensure we are not breaking things
with the release.

Thanks,
Shyam
___
maintainers mailing list
maintainers@gluster.org
https://lists.gluster.org/mailman/listinfo/maintainers

Re: [Gluster-Maintainers] Release 5: Missing option documentation (need inputs)

[Niels de Vos]

On Thu, Oct 11, 2018 at 09:00:50AM -0400, Shyam Ranganathan wrote:
> On 10/10/2018 11:20 PM, Atin Mukherjee wrote:
> > 
> > 
> > On Wed, 10 Oct 2018 at 20:30, Shyam Ranganathan  > > wrote:
> > 
> > The following options were added post 4.1 and are part of 5.0 as the
> > first release for the same. They were added in as part of bugs, and
> > hence looking at github issues to track them as enhancements did not
> > catch the same.
> > 
> > We need to document it in the release notes (and also the gluster doc.
> > site ideally), and hence I would like a some details on what to write
> > for the same (or release notes commits) for them.
> > 
> > Option: cluster.daemon-log-level
> > Attention: @atin
> > Review: https://review.gluster.org/c/glusterfs/+/20442
> > 
> > 
> > This option has to be used based on extreme need basis and this is why
> > it has been mentioned as GLOBAL_NO_DOC. So ideally this shouldn't be
> > documented.
> > 
> > Do we still want to capture it in the release notes?
> 
> This is an interesting catch-22, when we want users to use the option
> (say to provide better logs for troubleshooting), we have nothing to
> point to, and it would be instructions (repeated over the course of
> time) over mails.
> 
> I would look at adding this into an options section in the docs, but the
> best I can find in there is
> https://docs.gluster.org/en/latest/Administrator%20Guide/Managing%20Volumes/
> 
> I would say we need to improve the way we deal with options and the
> required submissions around the same.
> 
> Thoughts?

Maybe this should be documented under
https://docs.gluster.org/en/latest/Troubleshooting/ and not the general
"Managing Volumes" part of the docs.

Having it documented *somewhere* is definitely needed. And because it
seems to be related to debugging particular components, the
Troubleshooting section seems appropriate.

Niels
___
maintainers mailing list
maintainers@gluster.org
https://lists.gluster.org/mailman/listinfo/maintainers

Re: [Gluster-Maintainers] Release 5: Missing option documentation (need inputs)

[Nithya Balachandran]

On 11 October 2018 at 18:30, Shyam Ranganathan  wrote:

> On 10/10/2018 11:20 PM, Atin Mukherjee wrote:
> >
> >
> > On Wed, 10 Oct 2018 at 20:30, Shyam Ranganathan  > > wrote:
> >
> > The following options were added post 4.1 and are part of 5.0 as the
> > first release for the same. They were added in as part of bugs, and
> > hence looking at github issues to track them as enhancements did not
> > catch the same.
> >
> > We need to document it in the release notes (and also the gluster
> doc.
> > site ideally), and hence I would like a some details on what to write
> > for the same (or release notes commits) for them.
> >
> > Option: cluster.daemon-log-level
> > Attention: @atin
> > Review: https://review.gluster.org/c/glusterfs/+/20442
> >
> >
> > This option has to be used based on extreme need basis and this is why
> > it has been mentioned as GLOBAL_NO_DOC. So ideally this shouldn't be
> > documented.
> >
> > Do we still want to capture it in the release notes?
>
> This is an interesting catch-22, when we want users to use the option
> (say to provide better logs for troubleshooting), we have nothing to
> point to, and it would be instructions (repeated over the course of
> time) over mails.
>
> I would look at adding this into an options section in the docs, but the
> best I can find in there is
> https://docs.gluster.org/en/latest/Administrator%20Guide/
> Managing%20Volumes/
>
> I would say we need to improve the way we deal with options and the
> required submissions around the same.
>
> No argument there. I will take a look and get back on what we can improve
in the docs.



> Thoughts?
>
> >
> > 
> >
> > Option: ctime-invalidation
> > Attention: @Du
> > Review: https://review.gluster.org/c/glusterfs/+/20286
> >
> > Option: shard-lru-limit
> > Attention: @krutika
> > Review: https://review.gluster.org/c/glusterfs/+/20544
> >
> > Option: shard-deletion-rate
> > Attention: @krutika
> > Review: https://review.gluster.org/c/glusterfs/+/19970
> >
> > Please send in the required text ASAP, as we are almost towards the
> end
> > of the release.
> >
> > Thanks,
> > Shyam
> >
> ___
> maintainers mailing list
> maintainers@gluster.org
> https://lists.gluster.org/mailman/listinfo/maintainers
>
___
maintainers mailing list
maintainers@gluster.org
https://lists.gluster.org/mailman/listinfo/maintainers

Re: [Gluster-Maintainers] Release 5: Missing option documentation (need inputs)

[Shyam Ranganathan]

On 10/10/2018 11:20 PM, Atin Mukherjee wrote:
> 
> 
> On Wed, 10 Oct 2018 at 20:30, Shyam Ranganathan  > wrote:
> 
> The following options were added post 4.1 and are part of 5.0 as the
> first release for the same. They were added in as part of bugs, and
> hence looking at github issues to track them as enhancements did not
> catch the same.
> 
> We need to document it in the release notes (and also the gluster doc.
> site ideally), and hence I would like a some details on what to write
> for the same (or release notes commits) for them.
> 
> Option: cluster.daemon-log-level
> Attention: @atin
> Review: https://review.gluster.org/c/glusterfs/+/20442
> 
> 
> This option has to be used based on extreme need basis and this is why
> it has been mentioned as GLOBAL_NO_DOC. So ideally this shouldn't be
> documented.
> 
> Do we still want to capture it in the release notes?

This is an interesting catch-22, when we want users to use the option
(say to provide better logs for troubleshooting), we have nothing to
point to, and it would be instructions (repeated over the course of
time) over mails.

I would look at adding this into an options section in the docs, but the
best I can find in there is
https://docs.gluster.org/en/latest/Administrator%20Guide/Managing%20Volumes/

I would say we need to improve the way we deal with options and the
required submissions around the same.

Thoughts?

> 
> 
> 
> Option: ctime-invalidation
> Attention: @Du
> Review: https://review.gluster.org/c/glusterfs/+/20286
> 
> Option: shard-lru-limit
> Attention: @krutika
> Review: https://review.gluster.org/c/glusterfs/+/20544
> 
> Option: shard-deletion-rate
> Attention: @krutika
> Review: https://review.gluster.org/c/glusterfs/+/19970
> 
> Please send in the required text ASAP, as we are almost towards the end
> of the release.
> 
> Thanks,
> Shyam
> 
___
maintainers mailing list
maintainers@gluster.org
https://lists.gluster.org/mailman/listinfo/maintainers

Re: [Gluster-Maintainers] glusterfs-5.0rc1 released

[Niels de Vos]

On Wed, Oct 10, 2018 at 04:00:04PM -0400, Shyam Ranganathan wrote:
> On 10/10/2018 03:58 AM, Niels de Vos wrote:
> > On Fri, Oct 05, 2018 at 03:04:41PM -0400, Kaleb S. KEITHLEY wrote:
> >> On 10/5/18 12:44 PM, jenk...@build.gluster.org wrote:
> >>> SRC: 
> >>> https://build.gluster.org/job/release-new/71/artifact/glusterfs-5.0rc1.tar.gz
> >>> HASH: 
> >>> https://build.gluster.org/job/release-new/71/artifact/glusterfs-5.0rc1.sha512sum
> >>>
> >>> This release is made off jenkins-release-71
> >>>
> >> GlusterFS 5.0rc1 Packages for:
> >>
> >>   * el6, el7, el8 (CentOS, RHEL)...
> >>   * Fedora 27, 28, 29...
> >>   * Debian stretch/9, buster/10
> > 
> > And since Monday the CentOS Storage SIG packages are also available.
> > Sorry for forgetting to send out a note.
> > 
> > 1. install centos-release-gluster5:
> >- for CentOS-6: 
> > http://cbs.centos.org/kojifiles/packages/centos-release-gluster5/0.9/1.el6.centos/noarch/centos-release-gluster5-0.9-1.el6.centos.noarch.rpm
> >- for CentOS-7: 
> > http://cbs.centos.org/kojifiles/packages/centos-release-gluster5/0.9/1.el7.centos/noarch/centos-release-gluster5-0.9-1.el7.centos.noarch.rpm
> > 
> ># yum install ${CENTOS_RELEASE_GLUSTER5_URL}
> > 
> > 2. the centos-gluster5-test repository should be enabled by default, so
> > 
> ># yum install glusterfs-fuse
> > 
> > 3. report back to this email
> 
> Tested install, upgrade procedure with heal and other client IO traffic
> as well. All tests passed as required.

Thanks!
___
maintainers mailing list
maintainers@gluster.org
https://lists.gluster.org/mailman/listinfo/maintainers

Re: [Gluster-Maintainers] Release 5: Branched and further dates

[Xavi Hernandez]

On Wed, Oct 10, 2018 at 10:03 PM Shyam Ranganathan 
wrote:

> On 09/26/2018 10:21 AM, Shyam Ranganathan wrote:
> > 3. Upgrade testing
> >   - Need *volunteers* to do the upgrade testing as stated in the 4.1
> > upgrade guide [3] to note any differences or changes to the same
> >   - Explicit call out on *disperse* volumes, as we continue to state
> > online upgrade is not possible, is this addressed and can this be tested
> > and the documentation improved around the same?
>
> Completed upgrade testing using RC1 packages against a 4.1 cluster.
> Things hold up fine. (replicate type volumes)
>
> I have not attempted a rolling upgrade of disperse volumes, as we still
> lack instructions to do so. @Pranith/@Xavi is this feasible this release
> onward?
>

There were some problems with optimistic-change-log option. I think that
disabling it before upgrading (and give some time to become effective)
makes it possible to successfully complete a rolling upgrade, but I've not
tested it personally.

Adding @Ashish Pandey  who tested it, and may know
more details about the procedure.

Xavi


> Shyam
>
___
maintainers mailing list
maintainers@gluster.org
https://lists.gluster.org/mailman/listinfo/maintainers