On Mon, Feb 20, 2017 at 09:21:30PM -0500, Shyam wrote:
> Thanks Xavi, Looks good.
>
> Niels/Poornima,
>
> I would like to improve the release note on "Statedump support for gfapi
> based applications", it currently reads very poorly about the feature (I
> wrote it for RC0, so I know it is poor).
>
> Request one or both, of you to help with the same. Either submit a patch, or
> give me some notes that I can polish and commit.
What about this?
- - - %< - - -
### Statedump support for gfapi based applications
*Notes for users:*
gfapi based applications now can dump state information for better trouble
shooting of issues. A statedump can be triggered in two ways:
1. by executing `gluster volume statedump <VOL> client <HOST>:<PID>`
on one of the Gluster servers
- `<VOL>` should be replaced by the name of the volume
- `<HOST>` should be replaced by the hostname of the system running the
gfapi application
- `<PID>` should be replaced by the PID of the gfapi application
1. through calling `glfs_sysrq(<FS>, GLFS_SYSRQ_STATEDUMP)` within the
application
- `<FS>` should be replaced by a pointer to a `glfs_t` structure
All statedumps (`*.dump.*` files) will be located at the usual location,
on most distributions this would be `/var/run/gluster/`.
*Limitations:*
It is not possible to trigger statedumps from the Gluster CLI when the
gfapi application has lost its management connection to the GlusterD
servers.
GlusterFS 3.10 is the first release that contains support for the new
`glfs_sysrq()` function. Applications that include features for
debugging will need to be adapted to call this function. At the time of
the release of 3.10, no applications are known to call `glfs_sysrq()`.
*Known Issues:*
- - - >% - - -
Poornima, do you have anything to add/change?
Thanks,
Niels
>
> 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.
> >
> > Xavi
> >
> > [1] https://review.gluster.org/16685
> > [2] https://review.gluster.org/16614
> >
> > On 20/02/17 04:04, Shyam wrote:
> > > Hi,
> > >
> > > Please find the latest release notes for 3.10 here [1]
> > >
> > > This mail is to request feature owners, or folks who have tested to
> > > update the release notes (by sending gerrit commits to the same) for any
> > > updates that is desired (e.g feature related update, known issues in a
> > > feature etc.).
> > >
> > > 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:
> > > https://github.com/gluster/glusterfs/blob/release-3.10/doc/release-notes/3.10.0.md
> > >
> > >
> > >
> > > [2] Bug to use for release-notes updates:
> > > https://bugzilla.redhat.com/show_bug.cgi?id=1417735
> > >
> > > [3] Example release-note update:
> > > https://review.gluster.org/#/q/topic:bug-1417735
> > > _______________________________________________
> > > Gluster-devel mailing list
> > > Gluster-devel@xxxxxxxxxxx
> > > http://lists.gluster.org/mailman/listinfo/gluster-devel
> >
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-users
