search

strands-project / mongodb_store

MongoDB tools for storing and analysing runs of ROS systems.
BSD 3-Clause "New" or "Revised" License
49 stars 72 forks source link

Replicator node book keeping #145

Open hawesie opened 8 years ago

hawesie commented 8 years ago

It would be useful for the replicator node to keep track of what it actually replicates and when. This will allow an admin to check on the the operations performed and take action if necessary. Perhaps we should add a collection to the database where the replication is sent to in order to log replications? What do you think @marc-hanheide @cburbridge @furushchev ?

marc-hanheide commented 8 years ago

is that not actually what the oplog is for?

furushchev commented 8 years ago

I already do something like it: https://github.com/jsk-ros-pkg/jsk_robot/blob/master/jsk_robot_common/jsk_robot_startup/lifelog/periodic_replicator_client.py If we do anyway, It would be better to introduce "dynamic" book keeping. e.g.: start replication only when network traffic is much available, when logging data become big and need to replicate with delete_after_move=True, or when just idle.