+++ This bug was initially created as a clone of Bug #1468972 +++ Description of problem: Geo-replication log file naming should even be improved. It lacks filename readability. With current log file naming it is very difficult to relate it to what that log file is for.
Github tracker : https://github.com/gluster/glusterfs/issues/356
This will be fixed as part of major refactor patch for Geo-rep. As per commit message log file name changes are https://review.gluster.org/#/c/18257/ Both Master and Slave nodes will have subdir for session in the format "<mastervol>_<primary_slave_host>_<slavevol> - $GLUSTER_LOGDIR/geo-replication/<mastervol>_<primary_slave_host>_<slavevol> - $GLUSTER_LOGDIR/geo-replication-slaves/<mastervol>_<primary_slave_host>_<slavevol> Log file paths renamed since session info is available with directory name itself. $LOG_DIR_MASTER/ - gsyncd.log - Gsyncd, Worker monitor logs - mnt-<brick-path>.log - Aux mount logs, mounted by each worker - changes-<brick-path>.log - Changelog related logs(One per brick) $LOG_DIR_SLAVE/ - gsyncd.log - Slave Gsyncd logs - mnt-<master-node>-<master-brick-path>.log - Aux mount logs, mounted for each connection from master-node:master-brick - mnt-mbr-<master-node>-<master-brick-path>.log - Same as above, but mountbroker setup
This update is done in bulk based on the state of the patch and the time since last activity. If the issue is still seen, please reopen the bug.