I think it is a good idea to have the object-replicator's failure info 
in recon like the other replicators.

I think the following info can be added in object-replicator in addition to 
"object_replication_last" and "object_replication_time".

If there is any technical reason to not add them, I can make it. What do 
you think?

    "replication_last": 1416334368.60865,
    "replication_stats": {
        "attempted": 13346,
        "empty": 0,
        "failure": 870,
        "failure_nodes": {"": 3,
                          "": 860,
                          "": 7},
        "hashmatch": 0,
        "remove": 0,
        "start": 1416354240.9761429,
        "success": 1908
        "ts_repl": 0
    "replication_time": 2316.5563162644703,
    "object_replication_last": 1416334368.60865,
    "object_replication_time": 2316.5563162644703

Hisashi Osanai

On Tuesday, November 25, 2014 4:37 PM, Matsuda, Kenichiro 
[mailto:matsuda_keni...@jp.fujitsu.com] wrote:
> I understood that the logs are necessary to judge whether no failure on
> object-replicator.
> And also, I thought that the recon info of object-replicator having failure
> (just like the recon info of account-replicator and container-replicator)
> is useful.
> Are there any reason to not included failure in recon?

On Tuesday, November 25, 2014 5:53 AM, Clay Gerrard 
[mailto:clay.gerr...@gmail.com] wrote:
> > replication logs

On Friday, November 21, 2014 4:22 AM, Clay Gerrard 
[mailto:clay.gerr...@gmail.com] wrote:
> You might check if the swift-recon tool has the data you're looking for.  It 
> can report 
> the last completed replication pass time across nodes in the ring.

OpenStack-dev mailing list

Reply via email to