[
https://issues.apache.org/jira/browse/HDDS-2267?focusedWorklogId=327450&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-327450
]
ASF GitHub Bot logged work on HDDS-2267:
----------------------------------------
Author: ASF GitHub Bot
Created on: 13/Oct/19 07:33
Start Date: 13/Oct/19 07:33
Worklog Time Spent: 10m
Work Description: elek commented on issue #1624: HDDS-2267. Container
metadata scanner interval mismatch
URL: https://github.com/apache/hadoop/pull/1624#issuecomment-541394652
Thank you very much to open this pull request.
During the weekend the Ozone source code has been moved out from
[apache/hadoop](https://github.com/apache/hadoop) repository to
[apache/hadoop-ozone](https://github.com/apache/hadoop-ozone) repository.
This git commits are rewritten, but the branch of this pull request is also
transformed (state of Saturday morning), you can use the new, migrated branch
to recreate this pull request.
Your pull request is important for us: **Can you please re-create your pull
request in the new repository?**
**1**. Create a new fork of https://github.com/apache/hadoop-ozone
**2**. Clone it and have both your fork and the apache repo as remotes:
```
git clone g...@github.com:adoroszlai/hadoop-ozone.git
cd hadoop-ozone
git remote add apache g...@github.com:apache/hadoop-ozone.git
git fetch apache
```
**3**. Fetch your migrated branch and push it to your fork.
```
git checkout -b HDDS-2267 apache/HDDS-2267
git push origin HDDS-2267
```
**4**. And create the new pull request on the new repository.
https://github.com/apache/hadoop-ozone/compare/master...adoroszlai:HDDS-2267?expand=1
If you need more information, please check
[this](https://cwiki.apache.org/confluence/display/HADOOP/Hadoop+Ozone+source+tree+split)
wiki page or contact with me (my github user name + apache.org).
Thank you, and sorry for the inconvenience.
----------------------------------------------------------------
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
Issue Time Tracking
-------------------
Worklog Id: (was: 327450)
Time Spent: 40m (was: 0.5h)
> Container metadata scanner interval mismatch
> --------------------------------------------
>
> Key: HDDS-2267
> URL: https://issues.apache.org/jira/browse/HDDS-2267
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: Ozone Datanode
> Reporter: Attila Doroszlai
> Assignee: Attila Doroszlai
> Priority: Major
> Labels: pull-request-available
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Container metadata scanner can be configured to run at specific time
> intervals, eg. hourly ({{hdds.containerscrub.metadata.scan.interval}}).
> However, the actual run interval does not match the configuration. After a
> datanode restart, it runs in quick succession, later it runs at apparently
> random intervals.
> {noformat:title=sample log}
> datanode_1 | 2019-10-08 14:05:30 INFO ContainerMetadataScanner:88 -
> Completed an iteration of container metadata scrubber in 0 minutes. Number of
> iterations (since the data-node restart) : 1, Number of containers scanned
> in this iteration : 0, Number of unhealthy containers found in this iteration
> : 0
> datanode_1 | 2019-10-08 14:09:33 INFO ContainerMetadataScanner:88 -
> Completed an iteration of container metadata scrubber in 0 minutes. Number of
> iterations (since the data-node restart) : 1, Number of containers scanned
> in this iteration : 6, Number of unhealthy containers found in this iteration
> : 0
> ...
> datanode_1 | 2019-10-08 14:09:33 INFO ContainerMetadataScanner:88 -
> Completed an iteration of container metadata scrubber in 0 minutes. Number of
> iterations (since the data-node restart) : 28, Number of containers scanned
> in this iteration : 6, Number of unhealthy containers found in this iteration
> : 0
> datanode_1 | 2019-10-08 14:21:01 INFO ContainerMetadataScanner:88 -
> Completed an iteration of container metadata scrubber in 0 minutes. Number of
> iterations (since the data-node restart) : 29, Number of containers scanned
> in this iteration : 6, Number of unhealthy containers found in this iteration
> : 0
> datanode_1 | 2019-10-08 14:21:01 INFO ContainerMetadataScanner:88 -
> Completed an iteration of container metadata scrubber in 0 minutes. Number of
> iterations (since the data-node restart) : 30, Number of containers scanned
> in this iteration : 6, Number of unhealthy containers found in this iteration
> : 0
> datanode_1 | 2019-10-08 15:30:38 INFO ContainerMetadataScanner:88 -
> Completed an iteration of container metadata scrubber in 0 minutes. Number of
> iterations (since the data-node restart) : 31, Number of containers scanned
> in this iteration : 6, Number of unhealthy containers found in this iteration
> : 0
> datanode_1 | 2019-10-08 16:45:01 INFO ContainerMetadataScanner:88 -
> Completed an iteration of container metadata scrubber in 0 minutes. Number of
> iterations (since the data-node restart) : 32, Number of containers scanned
> in this iteration : 6, Number of unhealthy containers found in this iteration
> : 0
> {noformat}
> The problem is that time elapsed is measured in nanoseconds, while the
> configuration is in milliseconds.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
