Hi,
   below is error messages from datanode, we use CDH4 with redhat6.1, what
the problem?

[root@hadoop2 hadoop-hdfs]# tail -f hadoop-hdfs-datanode-hadoop2.log
2012-10-11 13:44:02,572 INFO
org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
new period : work left in prev period : 0.00%
2012-10-11 13:44:07,678 INFO
org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
new period : work left in prev period : 0.00%
2012-10-11 13:44:12,693 INFO
org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
new period : work left in prev period : 0.00%
2012-10-11 13:44:17,742 INFO
org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
new period : work left in prev period : 0.00%
2012-10-11 13:44:22,757 INFO
org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
new period : work left in prev period : 0.00%
2012-10-11 13:44:27,888 INFO
org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
new period : work left in prev period : 0.00%
2012-10-11 13:44:32,903 INFO
org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
new period : work left in prev period : 0.00%
2012-10-11 13:44:37,984 INFO
org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
new period : work left in prev period : 0.00%
2012-10-11 13:44:43,099 INFO
org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
new period : work left in prev period : 0.00%
2012-10-11 13:44:48,172 INFO
org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
new period : work left in prev period : 0.00%
2012-10-11 13:44:53,187 INFO
org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
new period : work left in prev period : 0.00%
2012-10-11 13:44:58,302 INFO
org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
new period : work left in prev period : 0.00%
2012-10-11 13:45:03,303 INFO
org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
new period : work left in prev period : 0.00%
2012-10-11 13:45:08,399 INFO
org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
new period : work left in prev period : 0.00%
2012-10-11 13:45:13,514 INFO
org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
new period : work left in prev period : 0.00%
2012-10-11 13:45:18,620 INFO
org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
new period : work left in prev period : 0.00%
2012-10-11 13:45:23,685 INFO
org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
new period : work left in prev period : 0.00%
2012-10-11 13:45:28,725 INFO
org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
new period : work left in prev period : 0.00%
2012-10-11 13:45:33,773 INFO
org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
new period : work left in prev period : 0.00%
2012-10-11 13:45:38,871 INFO
org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
new period : work left in prev period : 0.00%
2012-10-11 13:45:43,920 INFO
org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
new period : work left in prev period : 0.00%
2012-10-11 13:45:48,976 INFO
org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
new period : work left in prev period : 0.00%
2012-10-11 13:45:54,091 INFO
org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
new period : work left in prev period : 0.00%
2012-10-11 13:45:59,139 INFO
org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
new period : work left in prev period : 0.00%
2012-10-11 13:46:04,262 INFO
org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
new period : work left in prev period : 0.00%
2012-10-11 13:46:09,286 INFO
org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
new period : work left in prev period : 0.00%
2012-10-11 13:46:14,384 INFO
org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
new period : work left in prev period : 0.00%
2012-10-11 13:46:19,490 INFO
org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
new period : work left in prev period : 0.00%
2012-10-11 13:46:24,530 INFO
org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
new period : work left in prev period : 0.00%
2012-10-11 13:46:29,562 INFO
org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
new period : work left in prev period : 0.00%
2012-10-11 13:46:34,593 INFO
org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
new period : work left in prev period : 0.00%
2012-10-11 13:46:39,625 INFO
org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
new period : work left in prev period : 0.00%
2012-10-11 13:46:44,656 INFO
org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
new period : work left in prev period : 0.00%
2012-10-11 13:46:49,688 INFO
org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
new period : work left in prev period : 0.00%
2012-10-11 13:46:54,728 INFO
org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
new period : work left in prev period : 0.00%
2012-10-11 13:46:59,759 INFO
org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
new period : work left in prev period : 0.00%
2012-10-11 13:47:04,849 INFO
org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
new period : work left in prev period : 0.00%
2012-10-11 13:47:09,889 INFO
org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
new period : work left in prev period : 0.00%
2012-10-11 13:47:14,929 INFO
org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
new period : work left in prev period : 0.00%
2012-10-11 13:47:20,019 INFO
org.apache.hadoop.hdfs.server.datanod

Xiang,

Please do not use general@ for user-side issues. It exists for project
level discussions. I've moved your question to [EMAIL PROTECTED]
(https://groups.google.com/a/cloudera.org/forum/?fromgroups=#!topic/cdh-user)
as it may be a CDH specific thing you're asking about.

Regarding your log - I do not see any errors aside of the frequent
logging you're indicating. This frequent logging has been fixed in a
recent release of CDH4. You can disable the specific logging from
being shown via the DN's /logLevel servlet.

Perhaps if you can explain on the functional problem you are facing
(like reads or writes not working?) we can help better.

On Thu, Oct 11, 2012 at 11:19 AM, Xiang Hua <[EMAIL PROTECTED]> wrote:
> Hi,
>    below is error messages from datanode, we use CDH4 with redhat6.1, what
> the problem?
>
> [root@hadoop2 hadoop-hdfs]# tail -f hadoop-hdfs-datanode-hadoop2.log
> 2012-10-11 13:44:02,572 INFO
> org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
> new period : work left in prev period : 0.00%
> 2012-10-11 13:44:07,678 INFO
> org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
> new period : work left in prev period : 0.00%
> 2012-10-11 13:44:12,693 INFO
> org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
> new period : work left in prev period : 0.00%
> 2012-10-11 13:44:17,742 INFO
> org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
> new period : work left in prev period : 0.00%
> 2012-10-11 13:44:22,757 INFO
> org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
> new period : work left in prev period : 0.00%
> 2012-10-11 13:44:27,888 INFO
> org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
> new period : work left in prev period : 0.00%
> 2012-10-11 13:44:32,903 INFO
> org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
> new period : work left in prev period : 0.00%
> 2012-10-11 13:44:37,984 INFO
> org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
> new period : work left in prev period : 0.00%
> 2012-10-11 13:44:43,099 INFO
> org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
> new period : work left in prev period : 0.00%
> 2012-10-11 13:44:48,172 INFO
> org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
> new period : work left in prev period : 0.00%
> 2012-10-11 13:44:53,187 INFO
> org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
> new period : work left in prev period : 0.00%
> 2012-10-11 13:44:58,302 INFO
> org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
> new period : work left in prev period : 0.00%
> 2012-10-11 13:45:03,303 INFO
> org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
> new period : work left in prev period : 0.00%
> 2012-10-11 13:45:08,399 INFO
> org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
> new period : work left in prev period : 0.00%
> 2012-10-11 13:45:13,514 INFO
> org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
> new period : work left in prev period : 0.00%
> 2012-10-11 13:45:18,620 INFO
> org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
> new period : work left in prev period : 0.00%
> 2012-10-11 13:45:23,685 INFO
> org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
> new period : work left in prev period : 0.00%
> 2012-10-11 13:45:28,725 INFO
> org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
> new period : work left in prev period : 0.00%
> 2012-10-11 13:45:33,773 INFO
> org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
> new period : work left in prev period : 0.00%
> 2012-10-11 13:45:38,871 INFO
> org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
> new period : work left in prev period : 0.00%
> 2012-10-11 13:45:43,920 INFO

Harsh J

They are not errors, but I agree it's annoying.
See HDFS-3194 and HDFS-3828 for details.

Kihwal

On 10/11/12 12:49 AM, "Xiang Hua" <[EMAIL PROTECTED]> wrote:

>Hi,
>   below is error messages from datanode, we use CDH4 with redhat6.1, what
>the problem?
>
>[root@hadoop2 hadoop-hdfs]# tail -f hadoop-hdfs-datanode-hadoop2.log
>2012-10-11 13:44:02,572 INFO
>org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
>new period : work left in prev period : 0.00%
>2012-10-11 13:44:07,678 INFO
>org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
>new period : work left in prev period : 0.00%
>2012-10-11 13:44:12,693 INFO
>org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
>new period : work left in prev period : 0.00%
>2012-10-11 13:44:17,742 INFO
>org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
>new period : work left in prev period : 0.00%
>2012-10-11 13:44:22,757 INFO
>org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
>new period : work left in prev period : 0.00%
>2012-10-11 13:44:27,888 INFO
>org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
>new period : work left in prev period : 0.00%
>2012-10-11 13:44:32,903 INFO
>org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
>new period : work left in prev period : 0.00%
>2012-10-11 13:44:37,984 INFO
>org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
>new period : work left in prev period : 0.00%
>2012-10-11 13:44:43,099 INFO
>org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
>new period : work left in prev period : 0.00%
>2012-10-11 13:44:48,172 INFO
>org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
>new period : work left in prev period : 0.00%
>2012-10-11 13:44:53,187 INFO
>org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
>new period : work left in prev period : 0.00%
>2012-10-11 13:44:58,302 INFO
>org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
>new period : work left in prev period : 0.00%
>2012-10-11 13:45:03,303 INFO
>org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
>new period : work left in prev period : 0.00%
>2012-10-11 13:45:08,399 INFO
>org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
>new period : work left in prev period : 0.00%
>2012-10-11 13:45:13,514 INFO
>org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
>new period : work left in prev period : 0.00%
>2012-10-11 13:45:18,620 INFO
>org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
>new period : work left in prev period : 0.00%
>2012-10-11 13:45:23,685 INFO
>org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
>new period : work left in prev period : 0.00%
>2012-10-11 13:45:28,725 INFO
>org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
>new period : work left in prev period : 0.00%
>2012-10-11 13:45:33,773 INFO
>org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
>new period : work left in prev period : 0.00%
>2012-10-11 13:45:38,871 INFO
>org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
>new period : work left in prev period : 0.00%
>2012-10-11 13:45:43,920 INFO
>org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
>new period : work left in prev period : 0.00%
>2012-10-11 13:45:48,976 INFO
>org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
>new period : work left in prev period : 0.00%
>2012-10-11 13:45:54,091 INFO
>org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
>new period : work left in prev period : 0.00%
>2012-10-11 13:45:59,139 INFO
>org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a
>new period : work left in prev period : 0.00%
>2012-10-11 13:46:04,262 INFO
>org.apache.hadoop.hdfs.server.datanode.BlockPoolSliceScanner: Starting a