Closed Bug 993830 Opened 11 years ago Closed 6 years ago

Add recorded_ts to help replication slaves keep up to date [2 of 3]

Categories

(Testing :: General, defect)

Product:
Testing
Component:
General
Platform:
x86_64
Windows 7
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: ekyle, Unassigned)

References

(Blocks 1 open bug)

Details

BZ-ETL comes with a replication script (https://github.com/klahnakoski/Bugzilla-ETL/blob/master/bzETL/replicate.py). Replication has a few benefits: 1) The slave can have scripting enabled, allowing more powerful set of queries 2) Physical proximity increases the probability of reduced latency 3) The slave can be configured with better hardware 4) The slave's exclusivity increases availability (Mozilla's public cluster my have time of high load) Replication is a mess. The solution is to add another "recorded_ts" which records the time the record was updated. The slaves can probe this property for all new records, including records from a full ETL.
Blocks: 1110949
No longer blocks: 959670
Summary: Add recorded_ts to help replication slaves keep up to date → Add recorded_ts to help replication slaves keep up to date [2 of 3]
yes, this should be in the `etl.timestamp` property.
Blocks: 959670
No longer blocks: 1110949
done
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.