Description of problem: Current geo-replication logging is poor. Plenty of scope of geo-replication improvement. With the current log it is very difficult to understand the place of failure. Logging should be a bit more informative. Geo-replication log file naming should even be improved. It lacks filename readability. With file name it becomes very difficult to relate it with what that log file is for.
(In reply to Bipin Kunal from comment #0) > Description of problem: Current geo-replication logging is poor. Plenty of > scope of geo-replication improvement. > > With the current log it is very difficult to understand the place of > failure. Logging should be a bit more informative. Many patches merged in upstream with Log improvements, will include one more patch to address the review comments of patch https://review.gluster.org/#/c/17551/ > > Geo-replication log file naming should even be improved. It lacks filename > readability. With file name it becomes very difficult to relate it with what > that log file is for. This we can't implement in 3.4 release because file path change is not acceptable for 3.12 upstream(Already released, no path change will be accepted for minor release). Please open new RFE for the same.
The following patch is already in 3.3 which addresses few improvements. https://review.gluster.org/16997
Upstream patch https://review.gluster.org/#/c/17551/ is already available as part of rebase. Another patch sent to fix the remaining issues. https://review.gluster.org/19103
Downstream Patch https://code.engineering.redhat.com/gerrit/126634
(In reply to Aravinda VK from comment #3) > (In reply to Bipin Kunal from comment #0) > > Description of problem: Current geo-replication logging is poor. Plenty of > > scope of geo-replication improvement. > > > > With the current log it is very difficult to understand the place of > > failure. Logging should be a bit more informative. > > Many patches merged in upstream with Log improvements, will include one more > patch to address the review comments of patch > https://review.gluster.org/#/c/17551/ > > > > > Geo-replication log file naming should even be improved. It lacks filename > > readability. With file name it becomes very difficult to relate it with what > > that log file is for. > > This we can't implement in 3.4 release because file path change is not > acceptable for 3.12 upstream(Already released, no path change will be > accepted for minor release). Please open new RFE for the same. New RFE available here : https://bugzilla.redhat.com/show_bug.cgi?id=1512535
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2018:2607
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days