Member since
02-04-2016
189
Posts
70
Kudos Received
9
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
3741 | 07-12-2018 01:58 PM | |
7825 | 03-08-2018 10:44 AM | |
3745 | 06-24-2017 11:18 AM | |
23269 | 02-10-2017 04:54 PM | |
2286 | 01-19-2017 01:41 PM |
02-26-2016
03:38 PM
1 Kudo
I figured it out. Had to go to services->zookeeper and follow the menus. Any idea how to move the ambari metrics collector? I don't see any similar options.
... View more
02-26-2016
03:27 PM
1 Kudo
Actually, that isn't an option. Under "Host Actions", my options are: start all components stop all components restart all components turn on main. mode delete host set rack download client configs
... View more
02-26-2016
03:07 PM
1 Kudo
Interestingly, I don't see a dfs.datanode.balance.max.concurrent.moves property in our config. I do see dfs.datanode.balance.bandwidthPerSec Any idea what a good value for dfs.datanode.balance.max.concurrent.moves would be? I suppose it's a function of the number of data nodes.
... View more
02-26-2016
01:39 PM
1 Kudo
Thanks, @Artem Ervits. Do we need to stop any services, etc?
... View more
02-26-2016
01:38 PM
1 Kudo
Right. We should already have this bug fix.
... View more
02-26-2016
12:05 PM
3 Kudos
We recently tried to run the HDFS balancer for the first time. (Somehow we've been using HDP for almost 2 years and never knew that we should be doing this) After about an hour, it showed "5.56 GB moved / 12.72 TB left / 40 GB being processed". Now (10 hours later), it still says the same thing.
Does anyone know what the issue or solution here is? We're on 2.2.8 running in HA.
There's nothing in stderr. stdout is below.
[balancer] 16/02/24 21:11:51 WARN balancer.Dispatcher: Failed to move blk_1083404960_9672884 with size=134217728 from 10.22.4.44:50010:DISK to 10.22.6.22:50010:DISK through 10.22.4.46:50010: block move is failed: Not able to receive block 1083404960 from /10.22.4.64:38809 because threads quota is exceeded.
[balancer] 16/02/24 21:11:51 INFO balancer.Dispatcher: DDatanode:10.22.4.46:50010 activateDelay 10.0 seconds
16/02/24 21:11:51 WARN balancer.Dispatcher: Failed to move blk_1083404871_9672795 with size=134217728 from 10.22.4.44:50010:DISK to 10.22.6.22:50010:DISK through 10.22.4.44:50010: block move is failed: Not able to receive block 1083404871 from /10.22.4.64:38810 because threads quota is exceeded.
16/02/24 21:11:51 INFO balancer.Dispatcher: DDatanode:10.22.6.22:50010 activateDelay 10.0 seconds
[balancer] 16/02/24 21:11:51 INFO balancer.Dispatcher: DDatanode:10.22.4.44:50010 activateDelay 10.0 seconds
16/02/24 21:11:51 INFO balancer.Dispatcher: DDatanode:10.22.6.22:50010 activateDelay 10.0 seconds
[balancer] 16/02/24 21:11:56 INFO balancer.Dispatcher: Failed to find a pending move 5 times. Skipping 10.22.4.46:50010:DISK
[balancer] 16/02/24 21:11:56 INFO balancer.Dispatcher: Failed to find a pending move 5 times. Skipping 10.22.4.44:50010:DISK
[balancer] 16/02/24 21:11:57 INFO balancer.Dispatcher: Failed to find a pending move 5 times. Skipping 10.22.4.43:50010:DISK
[balancer] 16/02/24 21:11:57 INFO balancer.Dispatcher: Failed to find a pending move 5 times. Skipping 10.22.4.41:50010:DISK
... View more
Labels:
- Labels:
-
Apache Hadoop
02-26-2016
12:02 PM
3 Kudos
Many nodes and updates ago, when we first got started with Hadoop, we assigned one of our data nodes as a zookeeper server. I would like to move that to an edge node. Is there a document that outlines that steps to accomplish this? I'm on 2.2.8 Similarly, we need to move our ambari metrics server. Thanks!
... View more
Labels:
02-12-2016
10:55 AM
1 Kudo
Thanks Ian, Yes, to anyone experiencing the same behavior and looking for the solution, we simply needed to change the permissions on /mr-history in HDFS. Upgrading the timeline server to 1.5 was not necessary (and I couldn't get it to work).
... View more
02-10-2016
04:53 PM
1 Kudo
Thanks, Another followup: The instructions say: yarn.timeline-service.entity-group-fs-store.active-dir and yarn.timeline-service.entity-group-fs-store.done-dir must exist on the cluster on HDFS. Active-dir should have permission 01777, owned by YARN, group admin-group. Done-dir should have permission 0700, owned by yarn, group admin-group. 2 things: 1) 01777 isn't a valid permission set 2) when it says 'admin-group', does it literally mean that the group should be set to 'admin-group', or just a group with admin privileges? Almost everything in HDFS seems to be in either 'hadoop' or 'hdfs'.
... View more
02-10-2016
04:44 PM
1 Kudo
We don't have a dev cluster. I am the only one who needs the cluster today, so I can break stuff as long as it is put back together by tonight's ingest. It sounds like that's the only way I'm going to get this to work...
... View more
- « Previous
- Next »