big-data/hadoop
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

HDDS-1820. Fix numKeys metrics in OM HA. (#1116)

Browse Source
This commit is contained in:
Bharat Viswanadham 2019-07-18 09:36:15 -07:00 committed by GitHub
parent c34ceb5fde
commit f22818d0d6
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/request/key/OMKeyCommitRequest.java
View File

@ -178,6 +178,17 @@ public OMClientResponse validateAndUpdateCache(OzoneManager ozoneManager,
// return response after releasing lock. // return response after releasing lock.
if (exception == null) { if (exception == null) {
omResponse.setCommitKeyResponse(CommitKeyResponse.newBuilder().build()); omResponse.setCommitKeyResponse(CommitKeyResponse.newBuilder().build());
// As when we commit the key, then it is visible in ozone, so we should
// increment here.
// As key also can have multiple versions, we need to increment keys
// only if version is 0. Currently we have not complete support of
// versioning of keys. So, this can be revisited later.
if (omKeyInfo.getKeyLocationVersions().size() == 1) {
omMetrics.incNumKeys();
}
return new OMKeyCommitResponse(omKeyInfo, commitKeyRequest.getClientID(), return new OMKeyCommitResponse(omKeyInfo, commitKeyRequest.getClientID(),
omResponse.build()); omResponse.build());
} else { } else {