ChenSammi commented on pull request #1295:
URL: https://github.com/apache/hadoop-ozone/pull/1295#issuecomment-671699950
> However, there is another case where similar problem still exists: if key
is so large that it spans multiple blocks, `numberOfKeys` will include each
block separately.
>
> Test with patch using default block size of 256MB (after previous 64MB
test):
>
> ```
> $ ozone freon ockg -n1 -t1 -s 536870912 -p 512MB
> ...
> Successful executions: 1
>
> $ ozone admin container list
> {
> "state" : "OPEN",
> "replicationFactor" : "THREE",
> "replicationType" : "RATIS",
> "usedBytes" : 600834048,
> "numberOfKeys" : 3,
> "lastUsed" : "2020-08-10T08:32:43.112Z",
> "stateEnterTime" : "2020-08-10T08:22:39.855Z",
> "owner" : "f430cf45-c4ba-4271-8b3a-22bd314be60d",
> "containerID" : 1,
> "deleteTransactionId" : 0,
> "sequenceId" : 0,
> "open" : true
> }
> ```
>
> Here `numberOfKeys` should be 2, but it is 3 = 1 (for 64MB key) + 2 (for
512MB key).
@adoroszlai thanks for the review and comments. The keyCount in each
container is different from the keyCount from OM point of view. The keyCount
in container is actually the block count(FilePerBlock) or the chunk
count(FilePerChunk). So in the above case, 3 numberOfKeys is an expected
value.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
