Bug 1463496 - [Libgfapi Statedump] : Fix command help to work around the existing bottlenecks to take a statedump on gfapi applications.
[Libgfapi Statedump] : Fix command help to work around the existing bottlenec...
Status: CLOSED CANTFIX
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: libgfapi (Show other bugs)
3.3
x86_64 Linux
unspecified Severity medium
: ---
: ---
Assigned To: Niels de Vos
Ambarish
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-06-21 02:47 EDT by Ambarish
Modified: 2017-06-21 07:32 EDT (History)
11 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-06-21 07:32:31 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Ambarish 2017-06-21 02:47:49 EDT
Description of problem:
-----------------------

Couple of open issues on gfapi statedump that we haven't decided to fix:

https://bugzilla.redhat.com/show_bug.cgi?id=1454311
https://bugzilla.redhat.com/show_bug.cgi?id=1462079

This is the current command help :

[root@gqas013 ~]# gluster v statedump
Usage: volume statedump <VOLNAME> [[nfs|quotad] [all|mem|iobuf|callpool|priv|fd|inode|history]... | [client <hostname:process-id>]]
[root@gqas013 ~]# 

I'd suggest fixing the command help to work around these problems till we fix them,rather than documenting it in the guide.


Version-Release number of selected component (if applicable):
--------------------------------------------------------------

All 3.3 builds

How reproducible:
-----------------

Every time.
Comment 2 Niels de Vos 2017-06-21 04:16:40 EDT
(In reply to Ambarish from comment #0)
> I'd suggest fixing the command help to work around these problems till we
> fix them,rather than documenting it in the guide.

What is your recommendation for the help text?
Comment 3 Ambarish 2017-06-21 05:17:08 EDT
(In reply to Niels de Vos from comment #2)
> (In reply to Ambarish from comment #0)
> > I'd suggest fixing the command help to work around these problems till we
> > fix them,rather than documenting it in the guide.
> 
> What is your recommendation for the help text?

How about :

Usage: volume statedump <VOLNAME> [[nfs|quotad] [all|mem|iobuf|callpool|priv|fd|inode|history]... | [client <localhost:process-id>]]

This is the only way that works for Ganesha and Samba both.

Looping in Poornima too.
Comment 4 Niels de Vos 2017-06-21 05:44:24 EDT
The "localhost" is not correct if the application (like QEMU) mounts from an other storage server. We can not assume that all gfapi applications only mount from "localhost". There even is no requirement for applications to run on a storage server.

"localhost" can not be used for every gfapi use-case. What other alternative is there?
Comment 5 Atin Mukherjee 2017-06-21 07:20:55 EDT
IMHO, we can't fix this. I'd tend to close this bug if no objections by tomorrow. Do we have an agreement
Comment 6 Ambarish 2017-06-21 07:31:07 EDT
(In reply to Niels de Vos from comment #4)
> The "localhost" is not correct if the application (like QEMU) mounts from an
> other storage server. We can not assume that all gfapi applications only
> mount from "localhost". There even is no requirement for applications to run
> on a storage server.
> 
> "localhost" can not be used for every gfapi use-case. What other alternative
> is there?


Hmm..It cannot be used for _every_ gfapi use case,correct.

I guess this will have to be closed as Wont Fix.

Note You need to log in before you can comment on or make changes to this bug.