REVIEW: http://review.gluster.org/15064 (features/libgfchangelog: Log failure in gf_histroy_changelog) posted (#1) for review on master by Kotresh HR (firstname.lastname@example.org)
NOTE: The steps to reproduce mentioned in #Description is incorrect hence restating the problem description and steps to reproduce.
Description of problem:
If changelogs are not available for the requested time range, no proper error message is displayed. It just fails. If start time is less than min changelog available time, then history changelog fails with -1 as any failure and no error message is printed. Distinguishing this error will be helpful for
the consumers to act upon it.
For example, geo-replication upon receiving this error would fallback to
Version-Release number of selected component (if applicable):
Steps to Reproduce: (For simplicity consider plain distribute setup)
This is not simple to reproduce. It might hit during replace brick scencarios.
1. Setup geo-rep between master and slave
2. Before geo-rep syncs all data from master to slave, replace the brick from
master and write new data on master.
3. Now the replaced brick's min changelog available is much later than the
stime (sync time) corresponding to this brick.
4. When geo-rep is started after replace brick, it would hit above case.
When start time is less than min available changelog, histor fails with -1 and error is not logged.
It should distinguish the above error, log it and fail.
REVIEW: http://review.gluster.org/15064 (features/libgfchangelog: Log failure in gf_histroy_changelog) posted (#2) for review on master by Kotresh HR (email@example.com)
COMMIT: http://review.gluster.org/15064 committed in master by Aravinda VK (firstname.lastname@example.org)
Author: Kotresh HR <email@example.com>
Date: Mon Aug 1 16:59:33 2016 +0530
features/libgfchangelog: Log failure in gf_histroy_changelog
Add error logs if gf_history_changelog fails. If requested
changelog range is not available, log the error and exit
instead of continuing the loop and exiting in readdir
without logging. Also fixed the duplicate MSGID number in
Signed-off-by: Kotresh HR <firstname.lastname@example.org>
Smoke: Gluster Build System <email@example.com>
CentOS-regression: Gluster Build System <firstname.lastname@example.org>
NetBSD-regression: NetBSD Build System <email@example.com>
Reviewed-by: Aravinda VK <firstname.lastname@example.org>