You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "xuekaiqi (Jira)" <ji...@apache.org> on 2020/04/17 10:08:00 UTC
[jira] [Created] (KYLIN-4459) Continuous print warning
log-DFSInputStream has been closed already
xuekaiqi created KYLIN-4459:
-------------------------------
Summary: Continuous print warning log-DFSInputStream has been closed already
Key: KYLIN-4459
URL: https://issues.apache.org/jira/browse/KYLIN-4459
Project: Kylin
Issue Type: Improvement
Components: Storage - Parquet
Reporter: xuekaiqi
Assignee: wangrupeng
Fix For: v4.0.0
when starting kylin with debug tomcat mode, we can see these logs.
{code:java}
2020-03-12 10:17:06,082 ERROR [pool-12-thread-1] curator.CuratorScheduler:205 : Node(127.0.0.1) job server state conflict. Is ZK leader: true; Is active job server: false
2020-03-12 10:17:06,830 WARN [Curator-LeaderSelector-0] hdfs.DFSClient:669 : DFSInputStream has been closed already
2020-03-12 10:17:06,830 WARN [Curator-LeaderSelector-0] hdfs.DFSClient:669 : DFSInputStream has been closed already
2020-03-12 10:17:06,830 WARN [Curator-LeaderSelector-0] hdfs.DFSClient:669 : DFSInputStream has been closed already
2020-03-12 10:17:08,717 WARN [Curator-LeaderSelector-0] hdfs.DFSClient:669 : DFSInputStream has been closed already
2020-03-12 10:17:08,717 WARN [Curator-LeaderSelector-0] hdfs.DFSClient:669 : DFSInputStream has been closed already
2020-03-12 10:17:08,717 WARN [Curator-LeaderSelector-0] hdfs.DFSClient:669 : DFSInputStream has been closed already
2020-03-12 10:17:12,936 WARN [Curator-LeaderSelector-0] hdfs.DFSClient:669 : DFSInputStream has been closed already
2020-03-12 10:17:12,936 WARN [Curator-LeaderSelector-0] hdfs.DFSClient:669 : DFSInputStream has been closed already
2020-03-12 10:17:12,936 WARN [Curator-LeaderSelector-0] hdfs.DFSClient:669 : DFSInputStream has been closed already
2020-03-12 10:17:14,152 WARN [Curator-LeaderSelector-0] hdfs.DFSClient:669 : DFSInputStream has been closed already
2020-03-12 10:17:14,152 WARN [Curator-LeaderSelector-0] hdfs.DFSClient:669 : DFSInputStream has been closed already
2020-03-12 10:17:14,152 WARN [Curator-LeaderSelector-0] hdfs.DFSClient:669 : DFSInputStream has been closed already
2020-03-12 10:17:17,603 WARN [Curator-LeaderSelector-0] hdfs.DFSClient:669 : DFSInputStream has been closed already
2020-03-12 10:17:17,603 WARN [Curator-LeaderSelector-0] hdfs.DFSClient:669 : DFSInputStream has been closed already
2020-03-12 10:17:17,603 WARN [Curator-LeaderSelector-0] hdfs.DFSClient:669 : DFSInputStream has been closed already
2020-03-12 10:17:17,603 INFO [Curator-LeaderSelector-0] threadpool.DefaultScheduler:166 : Finishing resume all running jobs.
2020-03-12 10:17:17,603 INFO [Curator-LeaderSelector-0] threadpool.DefaultScheduler:170 : Fetching jobs every 30 seconds
2020-03-12 10:17:17,603 INFO [Curator-LeaderSelector-0] threadpool.DefaultScheduler:180 : Creating fetcher pool instance:2094578449
{code}
Upgrade hadoop version to 2.7.2 can fix it, but need more test in case some unpredictable problems
[https://community.cloudera.com/t5/Support-Questions/DFSInputStream-has-been-closed-already/td-p/125487]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)