and the theory so I'm not sure who created those
linkto files and why the linkto file are created.
I am going to leave this part as, dht_linkfile_create does this and
mostly would happen during lookup.
Shyam
___
Gluster-users mailing list
Gluster-users
will step up
the priority on this so that we have a clean fix that can be used to
prevent this in the future.
Shyam
___
Gluster-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users
trips to improve performance (next).
Foot note: None of this is ready yet, and would take time, this is just
a *possible* direction that gluster core is going ahead with to address
various problems at scale.
Shyam
[1]
http://www.gluster.org/community/documentation/index.php/Features/caching
1
client.event-threads: 1
In your gluster v info output then I think it will negate things. @Shyam - can
you confirm / deny this?
The change is to the *glusterd* vol file (by editing the same), so the
client and brick vol files should retain the event-threads as is.
-b
On Tue, Oct 13, 2
On 05/29/2016 10:08 PM, Sankarshan Mukhopadhyay wrote:
On Fri, May 20, 2016 at 7:30 PM, Shyam <srang...@redhat.com> wrote:
On 05/19/2016 10:25 PM, Pranith Kumar Karampuri wrote:
Once every 3 months i.e. option 3 sounds good to me.
+1 from my end.
Every 2 months seems to be a bit to
On 03/04/2016 07:30 AM, Pranith Kumar Karampuri wrote:
On 03/04/2016 05:47 PM, Bipin Kunal wrote:
HI Pranith,
Thanks for starting this mail thread.
Looking from a user perspective most important is to get a "good copy"
of data. I agree that people use replication for HA but having stale
On 03/05/2016 05:26 AM, Pranith Kumar Karampuri wrote:
That is the point. There is an illusion of choice between Data integrity
and HA. But we are not *really* giving HA, are we? HA will be there only
if second brick in the replica pair goes down. In your typical
@Pranith, can you elaborate on
On 05/19/2016 10:25 PM, Pranith Kumar Karampuri wrote:
Once every 3 months i.e. option 3 sounds good to me.
+1 from my end.
Every 2 months seems to be a bit too much, 4 months is still fine, but
gives us 1 in 3 to pick the LTS, I like 1:4 odds better for the LTS,
hence the 3 months (or
showing up the initial writes that were performed to
populate the volume.
From the code I do not see seek tracked in iostats, so it is not the
*seek* that is bloating these numbers up.
Regards,
Shyam
On 08/08/2016 04:47 PM, Jackie Tung wrote:
Hi,
I’m doing some benchmarking vs our trial
On 07/01/2016 01:45 AM, B.K.Raghuram wrote:
I have not gone through this implementation nor the new iscsi
implementation being worked on for 3.9 but I thought I'd share the
design behind a distributed iscsi implementation that we'd worked on
some time back based on the istgt code with a libgfapi
Release notes are still pending, other comments *inline*.
Tomorrow we will release beta1 for the package maintainers to roll out
the packages.
On 01/31/2017 08:42 PM, Shyam wrote:
Update day 2:
1) Brick multiplexing patch is merged into master, and now backported to
release-3.10. Yay
notes as commits, or respond here that there are none for their
feature. This is important for the beta.
Thanks,
Shyam
On 01/30/2017 02:55 PM, Shyam wrote:
Hi,
Before the release of 3.10 beta1, we are awaiting the merge of the
following commits on master, and a backport of the same into the 3.10
all is
highly appreciated.
For the antsy, git clone the repo and checkout v3.10.0rc0 tag to roll
your own builds and test. (doc/release-notes/3.10.0.md has the release
related features and bug fixes in it).
Thanks,
Shyam (Kaleb, Talur)
___
Gluster
in the
near future.
Thanks,
Shyam
[1] Release notes: https://review.gluster.org/16481
[2] Bug to update release notes:
https://bugzilla.redhat.com/show_bug.cgi?id=1417735
___
Gluster-users mailing list
Gluster-users@gluster.org
http://lists.gluster.org
an
option, clone the source and checkout tag v3.10.0rc1 [2]
Thanks,
Shyam (Kaleb, Talur)
[1] 3.10 Release notes:
https://github.com/gluster/glusterfs/blob/release-3.10/doc/release-notes/3.10.0.md
[2] Clone source from, `git clone https://github.com/gluster/glusterfs.git
me. Either submit a
patch, or give me some notes that I can polish and commit.
Thanks,
Shyam
On 02/20/2017 03:35 AM, Xavier Hernandez wrote:
Hi Shyam,
I've added some comments [1] for the issue between disperse's dynamic
code generator and SELinux. It assumes that [2] will be backported to 3.10.
Optionally try patching the sources with this commit and building,
https://review.gluster.org/#/c/15737/2
Shyam
On 02/09/2017 02:26 AM, Amudhan P wrote:
Hi All,
Using 'configure --disable-events` fixes above problem.
Thank you, Niklas for forwarding this info.
regards
Amudhan
On Sat, Dec
repository
Packages for ubuntu can be found here [2]
OpenSuSE pacjages can be found here [3]
CentOS packages should appear at [4] [5] soon
Thanks,
Shyam
[1] https://download.gluster.org/pub/gluster/glusterfs/3.10/3.10.0rc1/
[2] https://launchpad.net/~gluster/+archive/ubuntu/glusterfs-3.10
[3
.).
The release notes serve as our first point of public facing
documentation about what is in a release, so any and all feedback and
updates welcome here.
The bug ID to use for updating the release notes would be [2]
Example release notes commits are at [3]
Thanks,
Shyam
[1] Current release notes
/release-3.10/doc/release-notes/3.10.0.md
On 02/02/2017 10:12 PM, Shyam wrote:
Thanks to some last hour support from Jeff, Xavi, Nithya, Anoop, Kaleb
and a few others, we now have RC0 tagged, and on its way to package
maintainers.
Expect an official RC0 release announcement with packages in a day
On 01/17/2017 11:40 AM, Piotr Misiak wrote:
17 sty 2017 17:10 Jeff Darcy napisał(a):
Do you think that is wise to run rebalance process manually on every
brick with the actual commit hash value?
I didn't do anything with bricks after previous rebalance run and I have
Hi,
Thanks for all the work and attention towards 3.10 LTM release of
Gluster. The release packages have been built and a release
announcement, with the details, will be rolled out soon.
With this, here are some notes to remember,
1) The existing release bug tracker has been closed, and a
The Gluster community is pleased to announce the release of Gluster 3.10
(packages available at [1]).
This is a major Gluster release that includes some substantial changes.
The features revolve around, better support in container environments,
scaling to larger number of bricks per node, and
On 08/17/2016 10:21 AM, Atin Mukherjee wrote:
Here is one of the proposal from my end:
"Gluster maintainers responsibilities"
Theme - Process & Infrastructure
- Tracking incoming reviews and managing pending review backlogs with
the help of peer reviews/review marathon on a weekly basis
- Bug
Theme: Gluster.Next
Topic: "DHT2 - O Brother, Where Art Thou?"
Description:
An update on DHT2 design and it's progress, with the intention of
enabling discussions around the love or lack of the same, for the
proposed model.
Shyam
On 08/12/2016 03:48 PM, Vijay Bellur wrote
On 08/13/2016 03:59 AM, Niels de Vos wrote:
In addition to Vijays request to submit talks, I would like to see some
very specific topics presented/demo'd. Anyone attending the Summit and
willing to take these on is very much encouraged to do so. To do so,
reply to this (or Vijays) email with
On 10/13/2016 09:20 AM, Joe Julian wrote:
You forgot to count yourself: 6.
But still ... 6 when there was 60(?) in Berlin seems light. I know the
4am time doesn't work for the west coast of America, but that only
eliminates a very small percentage of those.
What's up, everyone else? Can
On 10/14/2016 10:48 AM, Manikandan Selvaganesh wrote:
Hi Soumya,
Welcome to the community.
Here[1] is the link for Gluster Documentation. I would suggest you to
google and
read a bit about GlusterFS and then get started with "Quick Start
Guide[2]".
Once you have done your setup and have played
:
- Primary: Shyam <srang...@redhat.com>
- Assisted by: Raghavendra Talur <rta...@redhat.com>
- Assisted by: Kaleb Keithly <kkeit...@redhat.com>
We are changing a few things on how we are managing this release, so if
you have features lined up for the release, read on!
Previousl
feature completion, so
that branching can happen on time.
Thank you,
Shyam
[1] Release 3.10 Project board:
https://github.com/gluster/glusterfs/projects/1
___
Gluster-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman
A) We need reviewers/maintainers to complete the reviews of the feature
pages that are under review, and get them to an accepted state.
B) We need the missing feature pages added, so that those can go through
the required reviews.
Just a reminder on the timelines, we have branching set to:
:
https://github.com/gluster/glusterfs/blob/release-3.10/doc/release-notes/3.10.1.md
Thanks,
Shyam
NOTE: Tracker bug for 3.10.1 will be closed in a couple of days and
tracker for 3.10.2 will be opened, and an announcement for 3.10.2 will
be sent with the details
, which we do not have. I
would suggest a github issue be added for such support, and take in the
prevention of current replace-brick on distribute only volumes as the
first priority (for obvious reasons as stated by talur).
Shyam
___
Gluster-users mai
On 03/27/2017 12:59 PM, Shyam wrote:
Hi,
It's time to prepare the 3.10.1 release, which falls on the 30th of each
month, and hence would be Mar-30th-2017 this time around.
We have one blocker issue for the release, which is [1] "auth failure
after upgrade to GlusterFS 3.10"
On 03/27/2017 03:25 PM, Gandalf Corvotempesta wrote:
2017-03-27 18:59 GMT+02:00 Shyam <srang...@redhat.com>:
1) Are there any pending *blocker* bugs that need to be tracked for 3.10.1?
If so mark them against the provided tracker [2] as blockers for the
release, or at the very least pos
Hi,
The first update for GlusterFS 3.10 is available. Packages for this
minor update are in the various repositories for the respective
distributions that the gluster community supports.
# Release notes for Gluster 3.10.1
This is a bugfix release. The release notes for [3.10.0](3.10.0.md),
On 04/17/2017 05:56 AM, Poornima Gurusiddaiah wrote:
Further to the above, we are also considering the following features for
this release, request feature owners to let us know if these are
actively being worked on and if these will make the branching dates.
(calling out folks that I think are
On 02/28/2017 10:17 AM, Shyam wrote:
Hi,
With release 3.10 shipped [1], it is time to set the dates for release
3.11 (and subsequently 4.0).
This mail has the following sections, so please read or revisit as needed,
- Release 3.11 dates (the schedule)
- 3.11 focus areas
Pinging the list
On 04/13/2017 11:32 AM, Atin Mukherjee wrote:
On Thu, Apr 13, 2017 at 8:17 PM, Shyam <srang...@redhat.com
<mailto:srang...@redhat.com>> wrote:
On 02/28/2017 10:17 AM, Shyam wrote:
Hi,
With release 3.10 shipped [1], it is time to set the dates for
On 02/28/2017 10:17 AM, Shyam wrote:
Hi,
With release 3.10 shipped [1], it is time to set the dates for release
3.11 (and subsequently 4.0).
This mail has the following sections, so please read or revisit as needed,
- 3.11 focus areas
- Release owners
Focusing on the above 2 sections
On 03/03/2017 06:44 AM, Prashanth Pai wrote:
On 02/28/2017 08:47 PM, Shyam wrote:
We should be transitioning to using github for feature reporting and
tracking, more fully from this release. So once again, if there exists
any confusion on that front, reach out to the lists for clarification
The Gluster community is pleased to announce the release of Gluster
3.11.1 (packages available at [1]).
Major changes and features (complete release notes can be found @ [2])
- Improved disperse (EC) volume performance
- Group settings for enabling negative lookup caching are provided
-
On 04/25/2017 10:08 AM, Shyam wrote:
On 04/25/2017 07:40 AM, Pranith Kumar Karampuri wrote:
On Thu, Apr 13, 2017 at 8:17 PM, Shyam <srang...@redhat.com
<mailto:srang...@redhat.com>> wrote:
On 02/28/2017 10:17 AM, Shyam wrote:
1) Halo - Initial Cut (@pranith)
Sorry f
On 04/26/2017 03:53 AM, Soumya Koduri wrote:
Hi Shyam,
On 04/25/2017 07:38 PM, Shyam wrote:
On 04/25/2017 07:40 AM, Pranith Kumar Karampuri wrote:
On Thu, Apr 13, 2017 at 8:17 PM, Shyam <srang...@redhat.com
<mailto:srang...@redhat.com>> wrote:
On 02/28/2017 10:17 AM, Shyam
On 04/25/2017 07:40 AM, Pranith Kumar Karampuri wrote:
On Thu, Apr 13, 2017 at 8:17 PM, Shyam <srang...@redhat.com
<mailto:srang...@redhat.com>> wrote:
On 02/28/2017 10:17 AM, Shyam wrote:
1) Halo - Initial Cut (@pranith)
Sorry for the delay in response. Due to som
, it is better as otherwise it is difficult
to use by the community.
Considering this, I would suggest we (as in all concerned) work on these
aspects and get it right in master before we take it in for a release.
Thanks,
Shyam
___
Gluster-users mailing list
against the release tracking bug [1].
Thanks,
Shyam
[1] Tracker BZ for 3.11.0 blockers:
https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-3.11.0
___
Gluster-users mailing list
Gluster-users@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster
are (still) signed with 3.10 signing key.
There will be a new signing key for the 3.11.0 GA and all following
3.11.X packages.
Request testing feedback from the community, that can help us catch any
major issue before the release.
Tracker BZ is at [2] and release notes are at [3]
Thanks,
Shyam
[5
Thanks Talur!
Further, for 3.10.3 as well Talur will be leading the release management
work and we intend to release it on time, this time :)
Shyam
On 05/14/2017 04:32 PM, Raghavendra Talur wrote:
Glusterfs 3.10.2 has been tagged.
Packages for the various distributions will be available
On 06/20/2017 08:41 AM, Pranith Kumar Karampuri wrote:
On Tue, Jun 6, 2017 at 6:54 PM, Shyam <srang...@redhat.com
<mailto:srang...@redhat.com>> wrote:
Hi,
It's time to prepare the 3.11.1 release, which falls on the 20th of
each month [4], and hence would be Ju
,
Shyam
[1] Bug awaiting fix: https://bugzilla.redhat.com/show_bug.cgi?id=1463250
"Releases are made better together"
On 06/06/2017 09:24 AM, Shyam wrote:
Hi,
It's time to prepare the 3.11.1 release, which falls on the 20th of
each month [4], and hence would be June-20th-2017 this t
On 06/21/2017 11:37 AM, Pranith Kumar Karampuri wrote:
On Tue, Jun 20, 2017 at 7:37 PM, Shyam <srang...@redhat.com
<mailto:srang...@redhat.com>> wrote:
Hi,
Release tagging has been postponed by a day to accommodate a fix for
a regression that has been introduced be
,
Shyam
On 06/05/2017 07:36 AM, Gandalf Corvotempesta wrote:
Great, thanks!
Il 5 giu 2017 6:49 AM, "Krutika Dhananjay" <kdhan...@redhat.com
<mailto:kdhan...@redhat.com>> ha scritto:
The fixes are already available in 3.10.2, 3.8.12 and 3.11.0
-Krutika
On Sun,
On 05/30/2017 08:44 PM, Zhang Huan wrote:
* Are there any existing users who need this enhancement?
https://bugzilla.redhat.com/show_bug.cgi?id=1358606#c27
Though not sure what branch Zhang Huan is on. @Zhang your inputs are
needed
here.
We are currently on 3.8. Thus the performance number is
need exceptions granted to make it into
the 3.12 release
- Release date: August 30th, 2017
Release owners:
- Shyam
- Any volunteers?
Features and major changes process in a nutshell:
1) Open a github issue
2) Refer the issue # in the commit messages of all changes against the
feature (specs
On 05/01/2017 01:13 PM, Pranith Kumar Karampuri wrote:
On Mon, May 1, 2017 at 10:42 PM, Pranith Kumar Karampuri
> wrote:
On Mon, May 1, 2017 at 10:39 PM, Gandalf Corvotempesta
On 05/01/2017 01:52 PM, Gandalf Corvotempesta wrote:
2017-05-01 19:50 GMT+02:00 Shyam <srang...@redhat.com>:
Splitting the bricks need not be a post factum decision, we can start with
larger brick counts, on a given node/disk count, and hence spread these
bricks to newer nodes/
On 05/01/2017 02:36 PM, Pranith Kumar Karampuri wrote:
On Tue, May 2, 2017 at 12:04 AM, Gandalf Corvotempesta
<gandalf.corvotempe...@gmail.com
<mailto:gandalf.corvotempe...@gmail.com>> wrote:
2017-05-01 20:30 GMT+02:00 Shyam <srang...@redhat.com
<mailto:s
On 05/01/2017 02:42 PM, Joe Julian wrote:
On 05/01/2017 11:36 AM, Pranith Kumar Karampuri wrote:
On Tue, May 2, 2017 at 12:04 AM, Gandalf Corvotempesta
<gandalf.corvotempe...@gmail.com
<mailto:gandalf.corvotempe...@gmail.com>> wrote:
2017-05-01 20:30 GMT+02:00
On 05/01/2017 02:23 PM, Pranith Kumar Karampuri wrote:
On Mon, May 1, 2017 at 11:43 PM, Shyam <srang...@redhat.com
<mailto:srang...@redhat.com>> wrote:
On 05/01/2017 02:00 PM, Pranith Kumar Karampuri wrote:
Splitting the bricks need not be a post factum deci
On 05/01/2017 02:42 PM, Pranith Kumar Karampuri wrote:
On Tue, May 2, 2017 at 12:07 AM, Shyam <srang...@redhat.com
<mailto:srang...@redhat.com>> wrote:
On 05/01/2017 02:23 PM, Pranith Kumar Karampuri wrote:
On Mon, May 1, 2017 at 11:43 PM, Shyam <sran
On 05/01/2017 02:47 PM, Pranith Kumar Karampuri wrote:
On Tue, May 2, 2017 at 12:14 AM, Shyam <srang...@redhat.com
<mailto:srang...@redhat.com>> wrote:
On 05/01/2017 02:42 PM, Pranith Kumar Karampuri wrote:
On Tue, May 2, 2017 at 12:07 AM, Shyam <sran
On 05/01/2017 02:25 PM, Gandalf Corvotempesta wrote:
2017-05-01 20:22 GMT+02:00 Shyam <srang...@redhat.com>:
Brick splitting (I think was first proposed by Jeff Darcy) is to create more
bricks out of given storage backends. IOW, instead of using a given brick as
is, create sub-dirs and us
On 05/01/2017 02:55 PM, Pranith Kumar Karampuri wrote:
On Tue, May 2, 2017 at 12:20 AM, Gandalf Corvotempesta
<gandalf.corvotempe...@gmail.com
<mailto:gandalf.corvotempe...@gmail.com>> wrote:
2017-05-01 20:43 GMT+02:00 Shyam <srang...@redhat.com
<mailto:srang...@red
rents #174 (@skoduri)
4) Halo - Initial version (@pranith)
Thanks,
Kaushal, Shyam
[1] 3.11 Branch: https://github.com/gluster/glusterfs/tree/release-3.11
[2] Tag for 3.11.0beta1 :
https://github.com/gluster/glusterfs/tree/v3.11.0beta1
[3] Tracker BZ for 3.11.0 blockers:
https://bugzilla.
mark it as blocking 3.10.2 release tracker bug.
Thanks,
Shyam
On 05/02/2017 06:20 AM, Pranith Kumar Karampuri wrote:
On Tue, May 2, 2017 at 9:16 AM, Pranith Kumar Karampuri
<pkara...@redhat.com <mailto:pkara...@redhat.com>> wrote:
Yeah it is a good idea. I asked him to raise
The Gluster community is pleased to announce the release of Gluster
3.11.0 (packages available at [1]).
This is a short term maintenance (STM) Gluster release that includes
some substantial changes. he features revolve around, improvements to
small file workloads, SE Linux support, Halo
and get
these going
3) Empty release notes are posted here [3], if there are any specific
call outs for 3.11 beyond bugs, please update the review, or leave a
comment in the review, for us to pick it up
Thanks,
Shyam/Kaushal
[1] Release bug tracker:
https://bugzilla.redhat.com/show_bug.cgi?id
.
thanks and regards
Shyam Deshmukh
___
Gluster-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users
http://pastebin.com/06LrDBYD
Here I have shared the log.
Please refer.
Thanks and regards
Shyam
On Sat, Mar 28, 2015 at 8:43 PM, Atin Mukherjee amukh...@redhat.com wrote:
What error are you getting trying to access the files. Could you also
share the client log file?
~Atin
On 03/28/2015
I'm sorry. I forgot to put error message.
Here is the error message in dialog box:
Unhandled error message: Error when getting information for file
'/home/server/data': No such file or directory
On Fri, Mar 27, 2015 at 8:42 PM, Shyam Deshmukh shyamdeshmukh...@gmail.com
wrote:
Hi all,
I have
Hi all,
Greetings ..
I tried to mounted volume. mount is successful. But files exist on mounted
volume are not available to access in client local folder.
Please tell me what could be possible error???
Thanks and regards
Shyam
___
Gluster-users
-a863-e9e8c4e84710
State: Peer in Cluster (Disconnected)
Hostname: gluster2
Uuid: 45ac276d-9e65-4e32-8abe-51f8ba0241ce
State: Peer in Cluster (Disconnected)
gluster@gluster1:~$
Thanks
Shyam
___
Gluster-users mailing list
Gluster-users@gluster.org
http
, confirmed that daemon is running. and also as per iptables
flush command.But it was not working.
Finally I created new nodes in virtual box and created new server pool.
Its working now.
Thanks..
Shyam D.
On Mon, Apr 20, 2015 at 10:09 AM, Sweta Anandpara sanan...@redhat.com
wrote:
Forgot to include
The Gluster community is pleased to announce the release of Gluster
3.11.2 (packages available at [1]).
Release notes for the release can be found at [2].
We still carry a major issue that is reported in the release-notes as
follows,
- Expanding a gluster volume that is sharded may cause
]. If it is
deemed as a blocker add it to the release tracker (or just drop a note
on the bug itself) [5].
Thanks,
Jiffin and Shyam.
[1] builds avaiable at:
https://download.gluster.org/pub/gluster/glusterfs/qa-releases/3.12.0rc0/
[2] Signing key for the builds:
https://download.gluster.org/pub/gluster
The Gluster community is pleased to announce the release of Gluster
3.10.5 (packages available at [1]).
Release notes for the release can be found at [2].
We are still awaiting feedback on a major issue that is reported in the
release-notes as follows, all known issues resulting in this
On 10/04/2017 06:17 AM, Niels de Vos wrote:
On Wed, Oct 04, 2017 at 09:44:44AM +, ismael mondiu wrote:
Hello,
I'd like to test if 3.10.6 version fixes the problem . I'm wondering which is
the correct way to upgrade from 3.10.5 to 3.10.6.
It's hard to find upgrade guides for a minor
The Gluster community is pleased to announce the release of Gluster
3.10.6 (packages available at [1]).
Release notes for the release can be found at [2].
We are still working on a further fix for the corruption issue when
sharded volumes are rebalanced, details as below.
* Expanding a
On 09/08/2017 01:32 PM, Serkan Çoban wrote:
Any suggestions?
On Thu, Sep 7, 2017 at 4:35 PM, Serkan Çoban wrote:
Hi,
Is it safe to use 3.10.5 client with 3.7.11 server with read-only data
move operation?
The normal upgrade, and hence tested, procedure is older
*1024) = 892MB/sec
Shyam
On 09/07/2017 12:07 AM, Serkan Çoban wrote:
It is sequential write with file size 2GB. Same behavior observed with
3.11.3 too.
On Thu, Sep 7, 2017 at 12:43 AM, Shyam Ranganathan <srang...@redhat.com> wrote:
On 09/06/2017 05:48 AM, Serkan Çoban wrote:
Hi,
Just d
equivalent to that to look at this further.
I would like to ensure there are no evident performance regressions as
you report.
Shyam
___
Gluster-users mailing list
Gluster-users@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-users
at ways to improve that in the future.
[1] https://buildlogs.centos.org/centos/6/storage/x86_64/gluster-3.12/
On Tue, Sep 5, 2017 at 8:11 PM, Shyam Ranganathan <srang...@redhat.com> wrote:
This is a major Gluster release that includes, features and bug fixes.
Notable feature high
This is a major Gluster release that includes, features and bug fixes.
Notable feature highlights are,
* Ability to mount sub-directories using the Gluster native
protocol (FUSE)
* Brick multiplexing enhancements that help scale to larger brick
counts per node
* Enhancements
The Gluster community is pleased to announce the release of Gluster
3.11.3 (packages available at [1,2,3]).
Release notes for the release can be found at [4].
***Reminder Number One***: 3.11.3 is the last release of the 3.11 STM
series. 3.11 will be EOL when 3.12 is released in a couple of
o straight from 3.8 to 3.10?
* Do I need to offline the volume first?
The upgrade notes [1] covers this, in short an offline upgrade is not
needed in your setup, as disperse is not a part of the stack.
Shyam
[1] 3.10 upgrade guide:
https://gluster.readthedocs.io/en/latest/Upgrade-Guide/upgra
On 08/28/2017 07:14 AM, Nigel Babu wrote:
Hello folks,
I spend some time today mucking about trying to figure out how to make
our documentation search a better experience. The short answer is,
search kind of works now.
Awesome! thank you.
Long answer: mkdocs creates a client side file
after release tagging (or the release announcement for that matter).
Thanks,
Shyam
___
Gluster-users mailing list
Gluster-users@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-users
The Gluster community is pleased to announce the release of Gluster
3.10.7 (packages available at [1]).
Release notes for the release can be found at [2].
We are still working on a further fix for the corruption issue when
sharded volumes are rebalanced, details as below.
* Expanding a
. There are a fair number of users in the community who have this
use-case and may have some interesting questions around the proposed method.
Shyam
___
Gluster-users mailing list
Gluster-users@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-users
compatibility concerns from a distribute
layer perspective in 4.0.
Thanks,
Shyam
___
Gluster-users mailing list
Gluster-users@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-users
This is a major release that includes a range of features enhancing
usability; enhancements to GFAPI for developers and a set of bug fixes.
* Addition of summary option to the heal info CLI
* Addition of checks for allowing lookups in AFR and removal of
'cluster.quorum-reads' volume option
The Gluster community is pleased to announce the release of Gluster
3.10.8 (packages available at [1]).
Release notes for the release can be found at [2].
We are still working on a further fix for the corruption issue when
sharded volumes are rebalanced, details as below.
* Expanding a
On 12/20/2017 01:01 AM, Hari Gowtham wrote:
> Yes Atin. I'll take a look.
Once we have a root cause and a way around, please document this in the
upgrade procedure in our docs as well. That way future problems have a
documented solution (outside of the lists as well).
Thanks!
>
> On Wed, Dec
On 12/20/2017 05:14 AM, Ravishankar N wrote:
> Hi,
>
> The existing syntax in the gluster CLI for creating arbiter volumes is
> `gluster volume create replica 3 arbiter 1 ` .
> It means (or at least intended to mean) that out of the 3 bricks, 1
> brick is the arbiter.
> There has been some
, 2018.
Thanks,
Shyam
On 04/30/2018 12:56 PM, Shyam Ranganathan wrote:
> The Gluster community is pleased to announce the release of Gluster
> 3.12.9 (packages available at [1]).
>
> Release notes for the release can be found at [2].
>
> This release contains fixes for CVE-2018-1088
in the month of May (slated on the
20th and 30th) were canceled.
Shyam
___
Gluster-users mailing list
Gluster-users@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-users
The Gluster community is pleased to announce the release of Gluster
3.10.12 (packages available at [1]).
Release notes for the release can be found at [2].
This release contains fixes for CVE-2018-1088 and CVE-2018-1112, among
other fixes. Please use the release notes to check on the fix list.
The Gluster community is pleased to announce the release of Gluster
3.12.9 (packages available at [1]).
Release notes for the release can be found at [2].
This release contains fixes for CVE-2018-1088 and CVE-2018-1112, among
other fixes. Please use the release notes to check on the fix list.
The Gluster community is pleased to announce the release of Gluster
4.0.2 (packages available at [1]).
Release notes for the release can be found at [2].
This release contains fixes for CVE-2018-1088 and CVE-2018-1112, among
other fixes. Please use the release notes to check on the fix list.
1 - 100 of 155 matches
Mail list logo