Bug #3304
closedReplication: Timed replication failures occur twice instead of once
0%
Description
This bug was first described in #3296, however I am opening a separate bug report for it because #3296 is more specific to LTER replication issues, while this bug is general to Metacat.
During a timed replication, documents that fail to replicate are sent a second time for no apparent reason. (Jing said he suspects this is a bug.) For example:
08-04-30 23:09:45 :: document ces_dataset.284.1 sent
08-04-30 23:09:48 :: document ces_dataset.285.1 sent
08-04-30 23:09:49 :: document ces_dataset.288.1 sent
08-04-30 23:09:50 :: document ces_dataset.291.1 sent
08-04-30 23:09:51 :: document ces_dataset.308.1 sent
08-04-30 23:10:01 :: document knb-lter-and.3190.4 sent
08-04-30 23:10:04 :: document knb-lter-and.3234.5 sent
.
.
.
08-05-01 04:26:29 :: document ces_dataset.284.1 sent
08-05-01 04:26:30 :: document ces_dataset.285.1 sent
08-05-01 04:26:31 :: document ces_dataset.288.1 sent
08-05-01 04:26:32 :: document ces_dataset.291.1 sent
08-05-01 04:26:33 :: document ces_dataset.308.1 sent
08-05-01 04:26:43 :: document knb-lter-and.3190.4 sent
08-05-01 04:26:45 :: document knb-lter-and.3234.5 sent
Replication from LTER to KNB takes about eleven hours to complete because of the large number of replication failures (see bug #3296). If documents were sent only once instead of twice, this time could be cut in half.
Related issues