[
https://issues.apache.org/jira/browse/HDFS-8681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14604522#comment-14604522
]
Arpit Agarwal edited comment on HDFS-8681 at 6/28/15 4:33 AM:
--------------------------------------------------------------
On further look here is the code from branch-2.6
{code}
long hours = conf.getInt(DFSConfigKeys.DFS_DATANODE_SCAN_PERIOD_HOURS_KEY,
DFSConfigKeys.DFS_DATANODE_SCAN_PERIOD_HOURS_DEFAULT);
if (hours <= 0) {
hours = DEFAULT_SCAN_PERIOD_HOURS;
}
{code}
where
{code}
private static final long DEFAULT_SCAN_PERIOD_HOURS = 21*24L; // three weeks
{code}
Looking into whether we can just restore this fallback to 3 weeks if the value
is un-configured or set to zero.
was (Author: arpitagarwal):
On further look here is t
> BlockScanner is incorrectly disabled by default
> -----------------------------------------------
>
> Key: HDFS-8681
> URL: https://issues.apache.org/jira/browse/HDFS-8681
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 2.7.0
> Reporter: Andrew Wang
> Assignee: Colin Patrick McCabe
> Priority: Blocker
> Attachments: HDFS-8681.01.patch
>
>
> This code is used to check whether the block scanner is enabled:
> {noformat}
> public boolean isEnabled() {
> return (conf.scanPeriodMs) > 0 && (conf.targetBytesPerSec > 0);
> }
> {noformat}
> Unfortunately, when this was introduced, we did not change the default scan
> period's value of 0, which means by default the BlockScanner is disabled.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
