Member since
05-11-2016
42
Posts
2
Kudos Received
3
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
2053 | 02-07-2018 06:22 AM | |
1664 | 11-13-2017 08:04 AM | |
1858 | 07-20-2017 03:01 AM |
08-06-2021
01:25 AM
Had the same issue on CDP 7.1.6, which comes with Tez 0.9.1. Looks like this: https://issues.apache.org/jira/browse/TEZ-4057 One workaround (probably not 100% secure) is to add the yarn user to the hive group: usermod -a -G hive yarn This needs to be done on all nodes and requires Yarn services restart. After that the issue has gone, no more random errors for Hive on Tez anymore.
... View more
09-02-2019
06:42 AM
Hi, Have you find a solution ? I have the same problem with my production cluster. HDFS HA is implemented from several years without problem. But recently, we realized that a hdfs client have to wait 20 secondes when the server hosting the nn1 is shutdown. Exemple when I set the debug mode : 19/08/29 11:03:05 DEBUG ipc.Client: Connecting to XXXXX/XXXXX:8020 19/08/29 11:03:23 DEBUG ipc.Client: Failed to connect to server: XXXXX/XXXXX:8020: try once and fail. java.net.NoRouteToHostException: No route to host Few informations : Hadoop version : 2.7.3 dfs.client.retry.policy.enabled : false dfs.client.failover.sleep.max.millis : 15000 ipc.client.connect.timeout : 20000 Thanks for your help !
... View more
03-29-2019
09:32 AM
1 Kudo
I had same issue and solved by changing "yarn.nodemanager.resource.memory-mb" from 468GB to 200GB with Amabri (There were following 11 changes.) (I shared it because it's really hard to find out the reason by reading error messages...)
... View more
02-07-2018
06:22 AM
I don't think so.
... View more
11-13-2017
08:04 AM
After upgrading our cluster from HDP 2.6.1 to HDP 2.6.2, the following WARN message is not output in NameNode's log. WARN org.apache.hadoop.hdfs.server.blockmanagement.BlockManager: Inconsistent number of corrupt replicas for blk_xxxx_xxxx blockMap has 0 but corrupt replicas map has 1
So, the problem seems to be fixed by this upgrading in our clusters.
... View more
09-08-2017
07:04 AM
I don't know more about this topic.any way thanks a lot for sharing such a useful post.i really like to read this article.here described informations are very useful for me.thanks a lot for sharing this post.i hope you more post. best gold necklace shop dubai
... View more
07-20-2017
03:01 AM
I think, no response means you guys do not recommend this my use case. I decided to follow install guide. Thanks!
... View more
07-11-2017
02:22 AM
np @Tomomichi Hirano feel free to accept best answer in this discussion thread so that other user can get benefit from it.
... View more
02-07-2018
06:19 AM
I had same problem "ranger can sync users with ldap but can't login to ranger UI with ldap password." Finally I could solved this problem, so, let me share lessons learned and how I solved to help you guys who has same problem as I faced. lessons learned 1. We have to configure ranger admin to speak ldaps protocol if we want to use ldaps for user authentication. paramaters in ranger-admin-site: ranger.truststore.file, ranger.truststore.password I had to import self-signed CA from LDAP team to "/etc/ranger/admin/conf/ranger-admin-keystore.jks". Set password which I specified for this import to "ranger.truststore.password". Command example: keytool -importcert -alias rangeradmin -noprompt -trustcacerts -file ./ca.crt -keystore /etc/ranger/admin/conf/ranger-admin-keystore.jks -storepass xasecure ref: https://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.6.0/bk_security/content/configure_non_ambari_ranger_ssl_self_signed_cert_admin.html 2. setting syncing user info with ldap and setting to use ldap for authentication are technically different. For example, we can use ldap authentication for ranger UI login even when we disable "Enable User Sync". In other words, we can use ldap authentication when "Ranger Usersync" service is not running. 3. debug logs from "org.springframework" and "org.apache.ranger" were very useful for the trouble shooting. We can change the log level with "admin-log4j.xml". log4j.category.org.springframework=debug,xa_log_appender log4j.category.org.apache.ranger=debug,xa_log_appender 4. Here are the key configurations for ldap authentication (not for user sync with ldap.) Authentication method: LDAP LDAP URL: ldaps://xxxxxx User Search Filter: (uid={0}) Group Search Filter: (member=uid={0},ou=xxxxx,o=xxxxx) ranger.ldap.user.dnpattern: uid={0},ou=xxxxx,o=xxxxx ranger.truststore.file: /etc/ranger/admin/conf/ranger-admin-keystore.jks <= in case with ldaps. ranger.truststore.password: xasecure <= in case with ldaps. this is the passwoed you set when you import ca to jks. I hope, this memo help guys who have same problem as I faced 🙂
... View more
06-08-2017
05:30 AM
Let me update this issue just for sharing. Actually, the block report problem was completely solved by updating HDP2.2 to HDP2.4. Thank you for your support.
... View more