release-notes: add status of gd2 and a highlights section
Change-Id: Idd4fd07b3fcdd7810c242eff0dcca9072048a43e fixes: bz#1672818 Signed-off-by: Amar Tumballi <amarts@redhat.com> Signed-off-by: ShyamsundarR <srangana@redhat.com>
This commit is contained in:
Amar Tumballi
ShyamsundarR
parent
c7a582818d
commit
1398fa8045
@ -1,9 +1,9 @@
|
||||
# Release notes for Gluster 6.0
|
||||
|
||||
This is a major release that includes a range of code improvements and stability
|
||||
fixes among a few features as noted below.
|
||||
fixes along with a few features as noted below.
|
||||
|
||||
A selection of the key features and changes are documented on this page.
|
||||
A selection of the key features and changes are documented in this page.
|
||||
A full list of bugs that have been addressed is included further below.
|
||||
|
||||
- [Announcements](#announcements)
|
||||
@ -16,8 +16,8 @@ A full list of bugs that have been addressed is included further below.
|
||||
1. Releases that receive maintenance updates post release 6 are, 4.1 and 5
|
||||
([reference](https://www.gluster.org/release-schedule/))
|
||||
|
||||
2. Release 6 will receive maintenance updates around the 30th of every month
|
||||
for the first 3 months post release (i.e Mar'19, Apr'19, May'19). Post the
|
||||
2. Release 6 will receive maintenance updates around the 10th of every month
|
||||
for the first 3 months post release (i.e Apr'19, May'19, Jun'19). Post the
|
||||
initial 3 months, it will receive maintenance updates every 2 months till EOL.
|
||||
([reference](https://lists.gluster.org/pipermail/announce/2018-July/000103.html))
|
||||
|
||||
@ -28,6 +28,7 @@ to the release 6 [upgrade guide](https://docs.gluster.org/en/latest/Upgrade-Guid
|
||||
This deprecation was announced at the gluster-users list [here](https://lists.gluster.org/pipermail/gluster-users/2018-July/034400.html).
|
||||
|
||||
Features deprecated:
|
||||
|
||||
- Block device (bd) xlator
|
||||
- Decompounder feature
|
||||
- Crypt xlator
|
||||
@ -37,6 +38,19 @@ Features deprecated:
|
||||
|
||||
## Major changes and features
|
||||
|
||||
### Highlights
|
||||
|
||||
- Several stability fixes addressing,
|
||||
- coverity, clang-scan, address sanitizer and valgrind reported issues
|
||||
- removal of unused and hence, deprecated code and features
|
||||
- Client side inode garbage collection
|
||||
- This release addresses one of the major concerns regarding FUSE mount
|
||||
process memory footprint, by introducing client side inode garbage collection
|
||||
- See [standalone](#standalone) section for more details
|
||||
- Performance Improvements
|
||||
- `--auto-invalidation` on FUSE mounts to leverage kernel page cache more
|
||||
effectively
|
||||
|
||||
Features are categorized into the following sections,
|
||||
|
||||
- [Management](#management)
|
||||
@ -45,19 +59,41 @@ Features are categorized into the following sections,
|
||||
|
||||
### Management
|
||||
|
||||
**NOTE:** There have been several stability improvements around the brick
|
||||
multiplexing feature
|
||||
|
||||
#### GlusterD2
|
||||
|
||||
TODO: Fill in GD2 status, as pertaining to GCS (container storage) release.
|
||||
GlusterD2 (or GD2, in short) was planned as the next generation management
|
||||
service for Gluster project.
|
||||
|
||||
Currently, GD2s main focus is not replacing `glusterd`, but to serve as a thin
|
||||
management layer when using gluster with container orchestration systems.
|
||||
|
||||
There is no specific update around GD2 provided as a part of this release.
|
||||
|
||||
### Standalone
|
||||
|
||||
#### 1. Glusterfind tool enhanced with a filter option
|
||||
#### 1. client-side inode garbage collection via LRU list
|
||||
|
||||
A FUSE mount's inode cache can now be limited to a maximum number, thus reducing
|
||||
the memory footprint of FUSE mount processes.
|
||||
|
||||
See the lru-limit option in `man 8 mount.glusterfs` for details.
|
||||
|
||||
NOTE: Setting this to a low value (say less than 4000), will evict inodes from
|
||||
FUSE and Gluster caches at a much faster rate, and can cause performance
|
||||
degrades. The setting has to be determined based on the available client memory
|
||||
and required performance.
|
||||
|
||||
#### 2. Glusterfind tool enhanced with a filter option
|
||||
|
||||
glusterfind tool has an added option "--type", to be used with the "--full"
|
||||
option. The option supports finding and listing files or directories only, and
|
||||
defaults to both if not specified.
|
||||
|
||||
Example usage with the pre and query commands are given below,
|
||||
|
||||
1. Pre command ([reference](https://docs.gluster.org/en/latest/GlusterFS%20Tools/glusterfind/#pre-command)):
|
||||
- Lists both files and directories in OUTFILE:
|
||||
`glusterfind pre SESSION_NAME VOLUME_NAME OUTFILE`
|
||||
@ -78,31 +114,20 @@ Example usage with the pre and query commands are given below,
|
||||
- Lists only directories in OUTFILE:
|
||||
`glusterfind query VOLUME_NAME --full --type d OUTFILE`
|
||||
|
||||
#### 2. FUSE mounts are enhanced to handle interrupts to blocked lock requests
|
||||
#### 3. FUSE mounts are enhanced to handle interrupts to blocked lock requests
|
||||
|
||||
FUSE mounts are enhanced to handle interrupts to blocked locks.
|
||||
|
||||
For example scripts using flock (`man 1 flock`) utility without the -n(nonblock)
|
||||
option against files on a FUSE based gluster mount, can now be interrupted when
|
||||
the lock is not granted in time or using the -w option from the same utility.
|
||||
|
||||
#### 3. client-side inode garbage collection via LRU list
|
||||
|
||||
A FUSE mounts inode cache can now be limited to a maximum number, thus reducing
|
||||
the memory footprint of FUSE mount processes.
|
||||
|
||||
See lru-limit option in `man 8 mount.glusterfs` for usage details.
|
||||
|
||||
NOTE: Setting this to low numbers (say less than 4000), will evict inodes from
|
||||
FUSE and Gluster caches at a much faster rate, and can cause performance
|
||||
degrades. The setting has to be balanced across available client memory and
|
||||
performance.
|
||||
For example, scripts using the flock (`man 1 flock`) utility without the
|
||||
-n(nonblock) option against files on a FUSE based gluster mount, can now be
|
||||
interrupted when the lock is not granted in time or using the -w option with
|
||||
the same utility.
|
||||
|
||||
#### 4. Optimized/pass-through distribute functionality for 1-way distributed volumes
|
||||
|
||||
**NOTE:** There are no user controllable changes with this feature
|
||||
|
||||
Distribute xlator is optimized, to mostly pass-through operations, when the
|
||||
The distribute xlator now skips unnecessary checks and operations when the
|
||||
distribute count is one for a volume, resulting in improved performance.
|
||||
|
||||
#### 5. Options introduced to disable invalidations of kernel page cache
|
||||
@ -138,7 +163,7 @@ remain unchanged.
|
||||
While configuring the sources for a build use the extra option `--enable-tsan`
|
||||
to enable thread sanitizer based builds.
|
||||
|
||||
#### 2. gfapi: A class of APIs have been enhances to return pre/post gluster_stat information
|
||||
#### 2. gfapi: A class of APIs have been enhanced to return pre/post gluster_stat information
|
||||
|
||||
A set of [apis](https://github.com/gluster/glusterfs/blob/release-6/api/src/gfapi.map#L245) have been enhanced to return pre/post gluster_stat information.
|
||||
Applications using gfapi would need to adapt to the newer interfaces to compile
|
||||
@ -147,7 +172,7 @@ older API SDK will continue to work as before.
|
||||
|
||||
## Major issues
|
||||
|
||||
<TODO>
|
||||
**None**
|
||||
|
||||
## Bugs addressed
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user