[Bugs] [Bug 1463191] gfapi: discard glfs object when volume is deleted

[bugzilla at redhat.com]

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

Niels de Vos <ndevos at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |amukherj at redhat.com,
                   |                            |ndevos at redhat.com,
                   |                            |rgowdapp at redhat.com
              Flags|                            |needinfo?(rgowdapp at redhat.c
                   |                            |om)
                   |                            |needinfo?(amukherj at redhat.c
                   |                            |om)



--- Comment #1 from Niels de Vos <ndevos at redhat.com> ---
This problem does not look like it is unique to gfapi, FUSE will most likely
have the same issue. Once a connection to a brick is dropped, a re-connect
should most likely verify if the volume-id is the same as before.

I think there are several approaches to solving this:

1. glusterd initiated through GF_CBK_EVENT_NOTIFY or similar (on volume delete)
2. handling this in protocol/client:RPC_CLNT_CONNECT and client_handshake()
3. in the master xlators like fuse and gfapi

Whatever is picked, any subsequent usage of the deleted volume should result in
ESTALE errors.


My current preference goes to doing this in protocol/client. What do others
think?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.