- android - RelativeLayout 背景可绘制重叠内容
- android - 如何链接 cpufeatures lib 以获取 native android 库?
- java - OnItemClickListener 不起作用,但 OnLongItemClickListener 在自定义 ListView 中起作用
- java - Android 文件转字符串
在我的主节点中运行 Hive 查询时,我遇到了一些严重的问题。我有 3 个集群设置(1 个名称节点,2 个数据节点)。
版本:
Hadoop:2.7.3
hive :2.1.0
Java:openjdk 版本“1.8.0_111”
操作系统:ubuntu 16.04.1
环境:亚马逊 EC2
我已经在主节点中安装了 Hive,并使用 start-dfs.sh 和 start-yarn.sh 从主节点启动了所有守护进程。我检查了主节点和从节点中的所有守护进程,都运行良好。当我连接到 Hive 并运行示例查询时,主节点中的所有守护进程都停止运行,但数据节点中的守护进程仍在运行。请从 hadoop-hduser-datanode-namenode.log 中找到以下日志详细信息。
2016-11-26 10:55:45,667 INFO org.apache.hadoop.http.HttpServer2: Jetty bound to port 45414
2016-11-26 10:55:45,667 INFO org.mortbay.log: jetty-6.1.26
2016-11-26 10:55:45,794 INFO org.mortbay.log: Started HttpServer2$SelectChannelConnectorWithSafeStartup@localhost:45414
2016-11-26 10:55:45,862 INFO org.apache.hadoop.hdfs.server.datanode.web.DatanodeHttpServer: Listening HTTP traffic on /0.0.0.0:50075
2016-11-26 10:55:45,913 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: dnUserName = user123
2016-11-26 10:55:45,913 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: supergroup = supergroup
2016-11-26 10:55:45,940 INFO org.apache.hadoop.ipc.CallQueueManager: Using callQueue class java.util.concurrent.LinkedBlockingQueue
2016-11-26 10:55:45,950 INFO org.apache.hadoop.ipc.Server: Starting Socket Reader #1 for port 50020
2016-11-26 10:55:45,970 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: Opened IPC server at /0.0.0.0:50020
2016-11-26 10:55:45,980 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: Refresh request received for nameservices: null
2016-11-26 10:55:46,000 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: Starting BPOfferServices for nameservices: <default>
2016-11-26 10:55:46,011 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: Block pool <registering> (Datanode Uuid unassigned) service to namenode/175.45.20.822:9000 starting to offer service
2016-11-26 10:55:46,022 INFO org.apache.hadoop.ipc.Server: IPC Server Responder: starting
2016-11-26 10:55:46,022 INFO org.apache.hadoop.ipc.Server: IPC Server listener on 50020: starting
2016-11-26 10:55:46,308 INFO org.apache.hadoop.hdfs.server.common.Storage: Using 1 threads to upgrade data directories (dfs.datanode.parallel.volumes.load.threads.num=1, dataDirs=1)
2016-11-26 10:55:46,315 INFO org.apache.hadoop.hdfs.server.common.Storage: Lock on /tmp/hadoop-user123/dfs/data/in_use.lock acquired by nodename 15455@namenode
2016-11-26 10:55:46,357 INFO org.apache.hadoop.hdfs.server.common.Storage: Analyzing storage directories for bpid BP-1195836218-175.45.20.822-1479972457866
2016-11-26 10:55:46,357 INFO org.apache.hadoop.hdfs.server.common.Storage: Locking is disabled for /tmp/hadoop-user123/dfs/data/current/BP-1195836218-175.45.20.822-1479972457866
2016-11-26 10:55:46,361 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: Setting up storage: nsid=148839353;bpid=BP-1195836218-175.45.20.822-1479972457866;lv=-56;nsInfo=lv=-63;cid=CID-c331d6bd-518b-4b20-a20b-b3bfb3c2896f;nsid=148839353;c=0;bpid=BP-1195836218-175.45.20.822-1479972457866;dnuuid=c98d92d6-14ac-4722-acb4-60727105f60c
2016-11-26 10:55:46,395 INFO org.apache.hadoop.hdfs.server.datanode.fsdataset.impl.FsDatasetImpl: Added new volume: DS-135f7e8e-5984-47e7-89f2-d41e1bf2cf36
2016-11-26 10:55:46,396 INFO org.apache.hadoop.hdfs.server.datanode.fsdataset.impl.FsDatasetImpl: Added volume - /tmp/hadoop-user123/dfs/data/current, StorageType: DISK
2016-11-26 10:55:46,401 INFO org.apache.hadoop.hdfs.server.datanode.fsdataset.impl.FsDatasetImpl: Registered FSDatasetState MBean
2016-11-26 10:55:46,402 INFO org.apache.hadoop.hdfs.server.datanode.fsdataset.impl.FsDatasetImpl: Adding block pool BP-1195836218-175.45.20.822-1479972457866
2016-11-26 10:55:46,403 INFO org.apache.hadoop.hdfs.server.datanode.fsdataset.impl.FsDatasetImpl: Scanning block pool BP-1195836218-175.45.20.822-1479972457866 on volume /tmp/hadoop-user123/dfs/data/current...
2016-11-26 10:55:46,413 INFO org.apache.hadoop.hdfs.server.datanode.fsdataset.impl.FsDatasetImpl: Time taken to scan block pool BP-1195836218-175.45.20.822-1479972457866 on /tmp/hadoop-user123/dfs/data/current: 11ms
2016-11-26 10:55:46,414 INFO org.apache.hadoop.hdfs.server.datanode.fsdataset.impl.FsDatasetImpl: Total time to scan all replicas for block pool BP-1195836218-175.45.20.822-1479972457866: 12ms
2016-11-26 10:55:46,414 INFO org.apache.hadoop.hdfs.server.datanode.fsdataset.impl.FsDatasetImpl: Adding replicas to map for block pool BP-1195836218-175.45.20.822-1479972457866 on volume /tmp/hadoop-user123/dfs/data/current...
2016-11-26 10:55:46,429 INFO org.apache.hadoop.hdfs.server.datanode.fsdataset.impl.FsDatasetImpl: Time to add replicas to map for block pool BP-1195836218-175.45.20.822-1479972457866 on volume /tmp/hadoop-user123/dfs/data/current: 15ms
2016-11-26 10:55:46,429 INFO org.apache.hadoop.hdfs.server.datanode.fsdataset.impl.FsDatasetImpl: Total time to add all replicas to map: 15ms
2016-11-26 10:55:46,497 INFO org.apache.hadoop.hdfs.server.datanode.VolumeScanner: VolumeScanner(/tmp/hadoop-user123/dfs/data, DS-135f7e8e-5984-47e7-89f2-d41e1bf2cf36): no suitable block pools found to scan. Waiting 1629134398 ms.
2016-11-26 10:55:46,499 INFO org.apache.hadoop.hdfs.server.datanode.DirectoryScanner: Periodic Directory Tree Verification scan starting at 1480165886499 with interval 21600000
2016-11-26 10:55:46,501 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: Block pool BP-1195836218-175.45.20.822-1479972457866 (Datanode Uuid null) service to namenode/175.45.20.822:9000 beginning handshake with NN
2016-11-26 10:55:46,510 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: Block pool Block pool BP-1195836218-175.45.20.822-1479972457866 (Datanode Uuid null) service to namenode/175.45.20.822:9000 successfully registered with NN
2016-11-26 10:55:46,510 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: For namenode namenode/175.45.20.822:9000 using DELETEREPORT_INTERVAL of 300000 msec BLOCKREPORT_INTERVAL of 21600000msec CACHEREPORT_INTERVAL of 10000msec Initial delay: 0msec; heartBeatInterval=3000
2016-11-26 10:55:46,563 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: Namenode Block pool BP-1195836218-175.45.20.822-1479972457866 (Datanode Uuid c98d92d6-14ac-4722-acb4-60727105f60c) service to namenode/175.45.20.822:9000 trying to claim ACTIVE state with txid=6318
2016-11-26 10:55:46,564 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: Acknowledging ACTIVE Namenode Block pool BP-1195836218-175.45.20.822-1479972457866 (Datanode Uuid c98d92d6-14ac-4722-acb4-60727105f60c) service to namenode/175.45.20.822:9000
2016-11-26 10:55:46,635 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: Successfully sent block report 0xe4aa15bb18cd, containing 1 storage report(s), of which we sent 1. The reports had 78 total blocks and used 1 RPC(s). This took 3 msec to generate and 68 msecs for RPC and NN processing. Got back one command: FinalizeCommand/5.
2016-11-26 10:55:46,636 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: Got finalize command for block pool BP-1195836218-175.45.20.822-1479972457866
2016-11-26 10:56:46,536 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: DatanodeRegistration(175.45.20.822:50010, datanodeUuid=c98d92d6-14ac-4722-acb4-60727105f60c, infoPort=50075, infoSecurePort=0, ipcPort=50020, storageInfo=lv=-56;cid=CID-c331d6bd-518b-4b20-a20b-b3bfb3c2896f;nsid=148839353;c=0) Starting thread to transfer BP-1195836218-175.45.20.822-1479972457866:blk_1073742505_1686 to 175.45.20.823:50010
2016-11-26 10:56:46,569 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: DataTransfer: Transmitted BP-1195836218-175.45.20.822-1479972457866:blk_1073742505_1686 (numBytes=5798) to /175.45.20.823:50010
2016-11-26 11:12:57,577 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: Receiving BP-1195836218-175.45.20.822-1479972457866:blk_1073742514_1695 src: /175.45.20.822:36416 dest: /175.45.20.822:50010
2016-11-26 11:12:57,669 INFO org.apache.hadoop.hdfs.server.datanode.DataNode.clienttrace: src: /175.45.20.822:36416, dest: /175.45.20.822:50010, bytes: 5780, op: HDFS_WRITE, cliID: DFSClient_NONMAPREDUCE_1542813275_1, offset: 0, srvID: c98d92d6-14ac-4722-acb4-60727105f60c, blockid: BP-1195836218-175.45.20.822-1479972457866:blk_1073742514_1695, duration: 68626648
2016-11-26 11:12:57,669 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: PacketResponder: BP-1195836218-175.45.20.822-1479972457866:blk_1073742514_1695, type=HAS_DOWNSTREAM_IN_PIPELINE terminating
2016-11-26 11:12:57,712 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: Receiving BP-1195836218-175.45.20.822-1479972457866:blk_1073742515_1696 src: /175.45.20.822:36420 dest: /175.45.20.822:50010
2016-11-26 11:12:57,795 INFO org.apache.hadoop.hdfs.server.datanode.DataNode.clienttrace: src: /175.45.20.822:36420, dest: /175.45.20.822:50010, bytes: 5175, op: HDFS_WRITE, cliID: DFSClient_NONMAPREDUCE_1542813275_1, offset: 0, srvID: c98d92d6-14ac-4722-acb4-60727105f60c, blockid: BP-1195836218-175.45.20.822-1479972457866:blk_1073742515_1696, duration: 38025952
2016-11-26 11:12:57,795 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: PacketResponder: BP-1195836218-175.45.20.822-1479972457866:blk_1073742515_1696, type=HAS_DOWNSTREAM_IN_PIPELINE terminating
2016-11-26 11:12:58,240 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: Receiving BP-1195836218-175.45.20.822-1479972457866:blk_1073742516_1697 src: /175.45.20.822:36426 dest: /175.45.20.822:50010
2016-11-26 11:12:58,564 INFO org.apache.hadoop.hdfs.server.datanode.DataNode.clienttrace: src: /175.45.20.822:36426, dest: /175.45.20.822:50010, bytes: 32414403, op: HDFS_WRITE, cliID: DFSClient_NONMAPREDUCE_1542813275_1, offset: 0, srvID: c98d92d6-14ac-4722-acb4-60727105f60c, blockid: BP-1195836218-175.45.20.822-1479972457866:blk_1073742516_1697, duration: 313068763
2016-11-26 11:12:58,564 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: PacketResponder: BP-1195836218-175.45.20.822-1479972457866:blk_1073742516_1697, type=HAS_DOWNSTREAM_IN_PIPELINE terminating
2016-11-26 11:12:58,627 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: Receiving BP-1195836218-175.45.20.822-1479972457866:blk_1073742517_1698 src: /175.45.20.822:36430 dest: /175.45.20.822:50010
2016-11-26 11:12:58,651 INFO org.apache.hadoop.hdfs.server.datanode.DataNode.clienttrace: src: /175.45.20.822:36430, dest: /175.45.20.822:50010, bytes: 498, op: HDFS_WRITE, cliID: DFSClient_NONMAPREDUCE_1542813275_1, offset: 0, srvID: c98d92d6-14ac-4722-acb4-60727105f60c, blockid: BP-1195836218-175.45.20.822-1479972457866:blk_1073742517_1698, duration: 7376542
2016-11-26 11:12:58,651 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: PacketResponder: BP-1195836218-175.45.20.822-1479972457866:blk_1073742517_1698, type=HAS_DOWNSTREAM_IN_PIPELINE terminating
2016-11-26 11:12:58,664 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: Receiving BP-1195836218-175.45.20.822-1479972457866:blk_1073742518_1699 src: /175.45.20.822:36434 dest: /175.45.20.822:50010
2016-11-26 11:12:58,677 INFO org.apache.hadoop.hdfs.server.datanode.DataNode.clienttrace: src: /175.45.20.822:36434, dest: /175.45.20.822:50010, bytes: 26, op: HDFS_WRITE, cliID: DFSClient_NONMAPREDUCE_1542813275_1, offset: 0, srvID: c98d92d6-14ac-4722-acb4-60727105f60c, blockid: BP-1195836218-175.45.20.822-1479972457866:blk_1073742518_1699, duration: 10092926
2016-11-26 11:12:58,677 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: PacketResponder: BP-1195836218-175.45.20.822-1479972457866:blk_1073742518_1699, type=HAS_DOWNSTREAM_IN_PIPELINE terminating
2016-11-26 11:12:58,723 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: Receiving BP-1195836218-175.45.20.822-1479972457866:blk_1073742519_1700 src: /175.45.20.822:36438 dest: /175.45.20.822:50010
2016-11-26 11:12:58,770 INFO org.apache.hadoop.hdfs.server.datanode.DataNode.clienttrace: src: /175.45.20.822:36438, dest: /175.45.20.822:50010, bytes: 240636, op: HDFS_WRITE, cliID: DFSClient_NONMAPREDUCE_1542813275_1, offset: 0, srvID: c98d92d6-14ac-4722-acb4-60727105f60c, blockid: BP-1195836218-175.45.20.822-1479972457866:blk_1073742519_1700, duration: 40609207
2016-11-26 11:12:58,770 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: PacketResponder: BP-1195836218-175.45.20.822-1479972457866:blk_1073742519_1700, type=HAS_DOWNSTREAM_IN_PIPELINE terminating
2016-11-26 11:13:04,927 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: Receiving BP-1195836218-175.45.20.822-1479972457866:blk_1073742520_1701 src: /175.45.20.822:36456 dest: /175.45.20.822:50010
2016-11-26 11:13:04,953 INFO org.apache.hadoop.hdfs.server.datanode.DataNode.clienttrace: src: /175.45.20.822:36456, dest: /175.45.20.822:50010, bytes: 275749, op: HDFS_WRITE, cliID: DFSClient_NONMAPREDUCE_230151483_1, offset: 0, srvID: c98d92d6-14ac-4722-acb4-60727105f60c, blockid: BP-1195836218-175.45.20.822-1479972457866:blk_1073742520_1701, duration: 21419056
2016-11-26 11:13:04,953 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: PacketResponder: BP-1195836218-175.45.20.822-1479972457866:blk_1073742520_1701, type=HAS_DOWNSTREAM_IN_PIPELINE terminating
2016-11-26 11:13:10,781 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: Receiving BP-1195836218-175.45.20.822-1479972457866:blk_1073742521_1702 src: /175.45.20.822:36466 dest: /175.45.20.822:50010
2016-11-26 11:13:16,567 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: DatanodeRegistration(175.45.20.822:50010, datanodeUuid=c98d92d6-14ac-4722-acb4-60727105f60c, infoPort=50075, infoSecurePort=0, ipcPort=50020, storageInfo=lv=-56;cid=CID-c331d6bd-518b-4b20-a20b-b3bfb3c2896f;nsid=148839353;c=0) Starting thread to transfer BP-1195836218-175.45.20.822-1479972457866:blk_1073742515_1696 to 175.45.20.823:50010
2016-11-26 11:13:16,568 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: DataTransfer: Transmitted BP-1195836218-175.45.20.822-1479972457866:blk_1073742515_1696 (numBytes=5175) to /175.45.20.823:50010
2016-11-26 11:13:18,158 INFO org.apache.hadoop.hdfs.server.datanode.DataNode.clienttrace: src: /175.45.20.822:36466, dest: /175.45.20.822:50010, bytes: 35339, op: HDFS_WRITE, cliID: DFSClient_NONMAPREDUCE_230151483_1, offset: 0, srvID: c98d92d6-14ac-4722-acb4-60727105f60c, blockid: BP-1195836218-175.45.20.822-1479972457866:blk_1073742521_1702, duration: 7374403211
2016-11-26 11:13:18,159 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: PacketResponder: BP-1195836218-175.45.20.822-1479972457866:blk_1073742521_1702, type=HAS_DOWNSTREAM_IN_PIPELINE terminating
2016-11-26 11:13:18,172 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: Receiving BP-1195836218-175.45.20.822-1479972457866:blk_1073742523_1704 src: /175.45.20.822:36476 dest: /175.45.20.822:50010
2016-11-26 11:13:18,182 INFO org.apache.hadoop.hdfs.server.datanode.DataNode.clienttrace: src: /175.45.20.822:36476, dest: /175.45.20.822:50010, bytes: 392, op: HDFS_WRITE, cliID: DFSClient_NONMAPREDUCE_230151483_1, offset: 0, srvID: c98d92d6-14ac-4722-acb4-60727105f60c, blockid: BP-1195836218-175.45.20.822-1479972457866:blk_1073742523_1704, duration: 7185360
2016-11-26 11:13:18,182 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: PacketResponder: BP-1195836218-175.45.20.822-1479972457866:blk_1073742523_1704, type=HAS_DOWNSTREAM_IN_PIPELINE terminating
2016-11-26 11:13:18,208 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: Receiving BP-1195836218-175.45.20.822-1479972457866:blk_1073742524_1705 src: /175.45.20.822:36482 dest: /175.45.20.822:50010
2016-11-26 11:13:18,215 INFO org.apache.hadoop.hdfs.server.datanode.DataNode.clienttrace: src: /175.45.20.822:36482, dest: /175.45.20.822:50010, bytes: 35339, op: HDFS_WRITE, cliID: DFSClient_NONMAPREDUCE_230151483_1, offset: 0, srvID: c98d92d6-14ac-4722-acb4-60727105f60c, blockid: BP-1195836218-175.45.20.822-1479972457866:blk_1073742524_1705, duration: 5068037
2016-11-26 11:13:18,215 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: PacketResponder: BP-1195836218-175.45.20.822-1479972457866:blk_1073742524_1705, type=HAS_DOWNSTREAM_IN_PIPELINE terminating
2016-11-26 11:13:18,232 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: Receiving BP-1195836218-175.45.20.822-1479972457866:blk_1073742525_1706 src: /175.45.20.822:36486 dest: /175.45.20.822:50010
2016-11-26 11:13:18,240 INFO org.apache.hadoop.hdfs.server.datanode.DataNode.clienttrace: src: /175.45.20.822:36486, dest: /175.45.20.822:50010, bytes: 275749, op: HDFS_WRITE, cliID: DFSClient_NONMAPREDUCE_230151483_1, offset: 0, srvID: c98d92d6-14ac-4722-acb4-60727105f60c, blockid: BP-1195836218-175.45.20.822-1479972457866:blk_1073742525_1706, duration: 6277417
2016-11-26 11:13:18,241 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: PacketResponder: BP-1195836218-175.45.20.822-1479972457866:blk_1073742525_1706, type=HAS_DOWNSTREAM_IN_PIPELINE terminating
2016-11-26 11:13:22,568 INFO org.apache.hadoop.hdfs.server.datanode.fsdataset.impl.FsDatasetAsyncDiskService: Scheduling blk_1073742514_1695 file /tmp/hadoop-user123/dfs/data/current/BP-1195836218-175.45.20.822-1479972457866/current/finalized/subdir0/subdir2/blk_1073742514 for deletion
2016-11-26 11:13:22,569 INFO org.apache.hadoop.hdfs.server.datanode.fsdataset.impl.FsDatasetAsyncDiskService: Scheduling blk_1073742515_1696 file /tmp/hadoop-user123/dfs/data/current/BP-1195836218-175.45.20.822-1479972457866/current/finalized/subdir0/subdir2/blk_1073742515 for deletion
2016-11-26 11:13:22,569 INFO org.apache.hadoop.hdfs.server.datanode.fsdataset.impl.FsDatasetAsyncDiskService: Scheduling blk_1073742516_1697 file /tmp/hadoop-user123/dfs/data/current/BP-1195836218-175.45.20.822-1479972457866/current/finalized/subdir0/subdir2/blk_1073742516 for deletion
2016-11-26 11:13:22,569 INFO org.apache.hadoop.hdfs.server.datanode.fsdataset.impl.FsDatasetAsyncDiskService: Scheduling blk_1073742517_1698 file /tmp/hadoop-user123/dfs/data/current/BP-1195836218-175.45.20.822-1479972457866/current/finalized/subdir0/subdir2/blk_1073742517 for deletion
2016-11-26 11:13:22,569 INFO org.apache.hadoop.hdfs.server.datanode.fsdataset.impl.FsDatasetAsyncDiskService: Scheduling blk_1073742518_1699 file /tmp/hadoop-user123/dfs/data/current/BP-1195836218-175.45.20.822-1479972457866/current/finalized/subdir0/subdir2/blk_1073742518 for deletion
2016-11-26 11:13:22,569 INFO org.apache.hadoop.hdfs.server.datanode.fsdataset.impl.FsDatasetAsyncDiskService: Scheduling blk_1073742519_1700 file /tmp/hadoop-user123/dfs/data/current/BP-1195836218-175.45.20.822-1479972457866/current/finalized/subdir0/subdir2/blk_1073742519 for deletion
2016-11-26 11:13:22,569 INFO org.apache.hadoop.hdfs.server.datanode.fsdataset.impl.FsDatasetAsyncDiskService: Scheduling blk_1073742520_1701 file /tmp/hadoop-user123/dfs/data/current/BP-1195836218-175.45.20.822-1479972457866/current/finalized/subdir0/subdir2/blk_1073742520 for deletion
2016-11-26 11:13:22,569 INFO org.apache.hadoop.hdfs.server.datanode.fsdataset.impl.FsDatasetAsyncDiskService: Scheduling blk_1073742521_1702 file /tmp/hadoop-user123/dfs/data/current/BP-1195836218-175.45.20.822-1479972457866/current/finalized/subdir0/subdir2/blk_1073742521 for deletion
2016-11-26 11:13:22,571 INFO org.apache.hadoop.hdfs.server.datanode.fsdataset.impl.FsDatasetAsyncDiskService: Deleted BP-1195836218-175.45.20.822-1479972457866 blk_1073742514_1695 file /tmp/hadoop-user123/dfs/data/current/BP-1195836218-175.45.20.822-1479972457866/current/finalized/subdir0/subdir2/blk_1073742514
2016-11-26 11:13:22,571 INFO org.apache.hadoop.hdfs.server.datanode.fsdataset.impl.FsDatasetAsyncDiskService: Deleted BP-1195836218-175.45.20.822-1479972457866 blk_1073742515_1696 file /tmp/hadoop-user123/dfs/data/current/BP-1195836218-175.45.20.822-1479972457866/current/finalized/subdir0/subdir2/blk_1073742515
2016-11-26 11:13:22,576 INFO org.apache.hadoop.hdfs.server.datanode.fsdataset.impl.FsDatasetAsyncDiskService: Deleted BP-1195836218-175.45.20.822-1479972457866 blk_1073742516_1697 file /tmp/hadoop-user123/dfs/data/current/BP-1195836218-175.45.20.822-1479972457866/current/finalized/subdir0/subdir2/blk_1073742516
2016-11-26 11:13:22,576 INFO org.apache.hadoop.hdfs.server.datanode.fsdataset.impl.FsDatasetAsyncDiskService: Deleted BP-1195836218-175.45.20.822-1479972457866 blk_1073742517_1698 file /tmp/hadoop-user123/dfs/data/current/BP-1195836218-175.45.20.822-1479972457866/current/finalized/subdir0/subdir2/blk_1073742517
2016-11-26 11:13:22,577 INFO org.apache.hadoop.hdfs.server.datanode.fsdataset.impl.FsDatasetAsyncDiskService: Deleted BP-1195836218-175.45.20.822-1479972457866 blk_1073742518_1699 file /tmp/hadoop-user123/dfs/data/current/BP-1195836218-175.45.20.822-1479972457866/current/finalized/subdir0/subdir2/blk_1073742518
2016-11-26 11:13:22,577 INFO org.apache.hadoop.hdfs.server.datanode.fsdataset.impl.FsDatasetAsyncDiskService: Deleted BP-1195836218-175.45.20.822-1479972457866 blk_1073742519_1700 file /tmp/hadoop-user123/dfs/data/current/BP-1195836218-175.45.20.822-1479972457866/current/finalized/subdir0/subdir2/blk_1073742519
2016-11-26 11:13:22,577 INFO org.apache.hadoop.hdfs.server.datanode.fsdataset.impl.FsDatasetAsyncDiskService: Deleted BP-1195836218-175.45.20.822-1479972457866 blk_1073742520_1701 file /tmp/hadoop-user123/dfs/data/current/BP-1195836218-175.45.20.822-1479972457866/current/finalized/subdir0/subdir2/blk_1073742520
2016-11-26 11:13:22,577 INFO org.apache.hadoop.hdfs.server.datanode.fsdataset.impl.FsDatasetAsyncDiskService: Deleted BP-1195836218-175.45.20.822-1479972457866 blk_1073742521_1702 file /tmp/hadoop-user123/dfs/data/current/BP-1195836218-175.45.20.822-1479972457866/current/finalized/subdir0/subdir2/blk_1073742521
2016-11-26 11:13:24,722 ERROR org.apache.hadoop.hdfs.server.datanode.DataNode: RECEIVED SIGNAL 15: SIGTERM
2016-11-26 11:13:24,727 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: SHUTDOWN_MSG:
/************************************************************
SHUTDOWN_MSG: Shutting down DataNode at namenode/175.45.20.822
************************************************************/<br>
提前致谢。
最佳答案
经过一番研究,我启动了名称节点中的所有守护进程并输入了以下命令,它运行良好。
hadoop dfsadmin -refreshNodes
谢谢
关于hadoop - 错误 org.apache.hadoop.hdfs.server.datanode.DataNode : RECEIVED SIGNAL 15: SIGTERM,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/40818108/
我们有数据(此时未分配)要转换/聚合/透视到 wazoo。 我在 www 上看了看,我问的所有答案都指向 hadoop 可扩展、运行便宜(没有 SQL 服务器机器和许可证)、快速(如果你有足够的数据)
这很明显,我们都同意我们可以将 HDFS + YARN + MapReduce 称为 Hadoop。但是,Hadoop 生态系统中的其他不同组合和其他产品会怎样? 例如,HDFS + YARN + S
如果 es-hadoop 只是连接到 HDFS 的 Hadoop 连接器,它如何支持 Hadoop 分析? 最佳答案 我假设您指的是 this project .在这种情况下,ES Hadoop 项目
看完this和 this论文,我决定我想在 MapReduce 上为大型数据集实现分布式体积渲染设置作为我的本科论文工作。 Hadoop 是一个合理的选择吗? Java 不会扼杀一些性能提升或使与 C
我一直在尝试查找有关如何通过命令行提交 hadoop 作业的信息。 我知道命令 - hadoop jar jar-file 主类输入输出 还有另一个命令,我正在尝试查找有关它的信息,但未能找到 - h
Hadoop 服务器在 Kubernetes 中。而Hadoop客户端位于外网。所以我尝试使用 kubernetes-service 来使用 Hadoop 服务器。但是 hadoop fs -put
有没有人遇到奇怪的环境问题,在调用 hadoop 命令时被迫使用 SU 而不是 SUDO? sudo su -c 'hadoop fs -ls /' hdfs Found 4 itemsdrwxr-x
在更改 mapred-site.xml 中的属性后,我给出了一个 tar.bz2 文件、.gz 和 tar.gz 文件作为输入。以上似乎都没有奏效。我假设这里发生的是 hadoop 作为输入读取的记录
如何在 Hadoop Pipes 中获取正在 hadoop 映射器 中执行的输入文件 名称? 我可以很容易地在基于 java 的 map reducer 中获取文件名,比如 FileSplit fil
我想使用 MapReduce 方法分析连续的数据流(通过 HTTP 访问),因此我一直在研究 Apache Hadoop。不幸的是,Hadoop 似乎期望以固定大小的输入文件开始作业,而不是能够在新数
名称节点可以执行任务吗?默认情况下,任务在集群的数据节点上执行。 最佳答案 假设您正在询问MapReduce ... 使用YARN,MapReduce任务在应用程序主数据库中执行,而不是在nameno
我有一个关系A包含 (zip-code). 我还有另一个关系B包含 (name:gender:zip-code) (x:m:1234) (y:f:1234) (z:m:1245) (s:f:1235)
我是hadoop地区的新手。您能帮我负责(k2,list[v2,v2,v2...])形式的输出(意味着将键及其所有关联值组合在一起)的责任是吗? 谢谢。 最佳答案 这是Hadoop的MapReduce
因此,我一直在尝试编写一个hadoop程序,该程序将输入作为一个包含许多文件的文件,并且我希望hadoop程序的输出仅是输入文件的一行。但是我还没有做到这一点。我也不想去 reducer 课。如果有人
我使用的输入文本文件的内容是 1 "Come 1 "Defects," 1 "I 1 "Information 1 "J" 2 "Plain 5 "Project 1
谁能告诉我以下grep命令的作用: $ bin/hadoop jar hadoop-*-examples.jar grep input output 'dfs[a-z.]+' 最佳答案 http:/
我不了解mapreducer的基本功能,mapreducer是否有助于将文件放入HDFS 或mapreducer仅有助于分析HDFS中现有文件中的内容 我对hadoop非常陌生,任何人都可以指导我理解
CopyFromLocal将从本地文件系统上载数据。 不要放会从任何文件上传数据,例如。本地FS,亚马逊S3 或仅来自本地fs ??? 最佳答案 请找到两个命令的用法。 put ======= Usa
我开始研究hadoop mapreduce。 我是Java和hadoop的初学者,并且了解hadoop mapreduce的编码,但是有兴趣了解它在云中的内部工作方式。 您能否分享一些很好的链接来说明
我一直在寻找Hadoop mapreduce类的类路径。我正在使用Hortonworks 2.2.4版沙箱。我需要这样的类路径来运行我的javac编译器: javac -cp (CLASS_PATH)
我是一名优秀的程序员,十分优秀!