|author||Venkatesh Somyajulu <email@example.com>||2013-05-07 13:09:05 +0530|
|committer||Vijay Bellur <firstname.lastname@example.org>||2013-05-28 04:38:25 -0700|
protocol/client: Prevent excessive logging of client's "disconnect" messages.
Problem: Currently when gluster volume start force is executed, client process will talk to glusterd to get the port of the brick. But if brick's path is not available it cannot return brick's port. So client process will keep connecting and disconnecting from glusterd for port-query which is ultimately responsible for execssive logging of disconnect messages. Fix: Message will be logged just once at INFO level after the first disconnect from glusterd. Afterwards "disconnect" messages will be logged in DEBUG mode. Change-Id: I2b787f3820b5da45e090c562e5698fcfe24a02cd BUG: 959969 Signed-off-by: Venkatesh Somyajulu <email@example.com> Reviewed-on: http://review.gluster.org/4953 Reviewed-by: Amar Tumballi <firstname.lastname@example.org> Reviewed-by: Pranith Kumar Karampuri <email@example.com> Tested-by: Gluster Build System <firstname.lastname@example.org> Reviewed-by: Vijay Bellur <email@example.com>
Diffstat (limited to 'doc')
0 files changed, 0 insertions, 0 deletions