[
https://issues.apache.org/jira/browse/RATIS-652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16953166#comment-16953166
]
Hadoop QA commented on RATIS-652:
---------------------------------
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 5s{color}
| {color:red} RATIS-652 does not apply to master. Rebase required? Wrong
Branch? See https://yetus.apache.org/documentation/0.8.0/precommit-patchnames
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | RATIS-652 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12983213/RATIS-652-000.patch |
| Console output |
https://builds.apache.org/job/PreCommit-RATIS-Build/1070/console |
| Powered by | Apache Yetus 0.8.0 http://yetus.apache.org |
This message was automatically generated.
> Add metrics related to snapshot and log purge
> ---------------------------------------------
>
> Key: RATIS-652
> URL: https://issues.apache.org/jira/browse/RATIS-652
> Project: Ratis
> Issue Type: Sub-task
> Components: server
> Reporter: Shashikant Banerjee
> Assignee: Aravindan Vijayan
> Priority: Major
> Fix For: 0.5.0
>
> Attachments: RATIS-652-000.patch
>
>
> Following metrics would be good to determine overall snapshot and log purge
> behaviour of a ratis pipeline:
>
> |takeSnapshotLatency|Time taken to take a ratis snapshot.|
> |numSnapshots|Number of snapshots taken |
> |purgeLogRecordLatency|Time taken to purge logRecords.|
> |numPurgeLogCalls|Number of Purge log calls|
> |numInstallSnapshotOps|Number of install snapshot calls|
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
