[Bugs] [Bug 1627639] New: libgfchangelog: History API fails

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1627639

            Bug ID: 1627639
           Summary: libgfchangelog: History API fails
           Product: Red Hat Gluster Storage
           Version: 3.4
         Component: geo-replication
          Assignee: khiremat at redhat.com
          Reporter: sunkumar at redhat.com
        QA Contact: rhinduja at redhat.com
                CC: avishwan at redhat.com, bugs at gluster.org,
                    csaba at redhat.com, khiremat at redhat.com,
                    rhs-bugs at redhat.com, sankarshan at redhat.com,
                    storage-qa-internal at redhat.com, sunkumar at redhat.com
        Depends On: 1622549



+++ This bug was initially created as a clone of Bug #1622549 +++

Description of problem:
If requested start time and end time doesn't fall into
first HTIME file, then history API fails even though
continuous changelogs are avaiable for the requested range
in other HTIME files. This is induced by changelog disable
and enable which creates fresh HTIME index file.


Version-Release number of selected component (if applicable):
mainline

How reproducible:
Always

Steps to Reproduce:
1. Setup gluster volume and let the I/O happen
2. Enable changelog
3. sleep for some time
4. Disable changelog
5. sleep for sometime
6. Enable changelog
7. Use the sample c program attached to query history API with start time after
step 6



Actual results:
History fails

Expected results:
History API should not fail if continuous changelogs are available even if it's
second HTIME file.


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1622549
[Bug 1622549] libgfchangelog: History API fails
-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=BZHU1h2wT2&a=cc_unsubscribe