more fidelity in the recon's seems fine, statsd emissions are also a
popular target for telemetry radiation.
On Thu, Nov 27, 2014 at 5:01 AM, Osanai, Hisashi
osanai.hisa...@jp.fujitsu.com wrote:
Hi,
I think it is a good idea to have the object-replicator's failure info
in recon like the
Thank you for the response.
I updated the following patch with the idea.
https://review.openstack.org/#/c/138342/
On Friday, December 05, 2014 5:50 AM, Clay Gerrard wrote:
more fidelity in the recon's seems fine, statsd emissions are
also a popular target for telemetry radiation.
Thanks
Hi,
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
replication logs
On Thu, Nov 20, 2014 at 9:32 PM, Matsuda, Kenichiro
matsuda_keni...@jp.fujitsu.com wrote:
Hi,
Thank you for the info.
I was able to get replication info easily by swift-recon API.
But, I wasn't able to judge whether no failure from recon info of
object-replicator.
Hi,
Thanks for your advice.
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
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.
On Thu, Nov 20, 2014 at 1:28 AM, Matsuda, Kenichiro
matsuda_keni...@jp.fujitsu.com wrote:
Hi,
I would like to know about a way of checking
Hi,
Thank you for the info.
I was able to get replication info easily by swift-recon API.
But, I wasn't able to judge whether no failure from recon info of
object-replicator.
Could you please advise me for a way of get object-replicator's failure info?
[replication info from recon]
* account
