Just so I am clear the upgrade process will be as follows:
upgrade all clients to 4.0
rolling upgrade all servers to 4.0 (with GD1)
kill all GD1 daemons on all servers and run upgrade script (new clients
unable to connect at this point)
start GD2 ( necessary or does the upgrade script do this?)
I propose a talk
"Life of a gluster client process"
We will have a look at one complete life cycle of a client process
which includes:
* mount script and parsing of args
* contacting glusterd and fetching volfile
* loading and initializing the xlators
* how glusterd sends updates of volume option
On Thu, Nov 2, 2017 at 7:53 PM, Darrell Budic wrote:
> Will the various client packages (centos in my case) be able to
> automatically handle the upgrade vs new install decision, or will we be
> required to do something manually to determine that?
We should be able to do this with CentOS (and oth
Hi,
I just filled this bug, which seems to be related:
https://bugzilla.redhat.com/show_bug.cgi?id=1509071
Cheers,
Hans Henrik
On 27-07-2017 15:53, Mohammed Rafi K C wrote:
> Are you still facing the problem ? If so, Can you please provide the
> workload , cmd_log_history file, log files , etc