Member since
04-25-2016
579
Posts
609
Kudos Received
111
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 2933 | 02-12-2020 03:17 PM | |
| 2138 | 08-10-2017 09:42 AM | |
| 12483 | 07-28-2017 03:57 AM | |
| 3427 | 07-19-2017 02:43 AM | |
| 2528 | 07-13-2017 11:42 AM |
12-19-2016
03:19 PM
this is the link for Dockerized hdp version https://github.com/randerzander/docker-hdp you can install docker sandbox for HDP-2.5 has atlas already installed on it. https://community.hortonworks.com/articles/58458/installing-docker-version-of-sandbox-on-mac.html
... View more
12-19-2016
02:25 PM
1 Kudo
it looks yum is not able to findout the repo or repo is not setup correctly, could you please run a yum repolist command on ambari node to ensure the Ambari / HDP stack are configured correctly, your repo should point to HDP-2.5.3.0
... View more
12-19-2016
01:45 PM
2 Kudos
what is yarn.scheduler.minimum-allocation-mb set to? in your case it looks yarn.scheduler.minimum-allocation-mb is set too high and you are trying to set hive.tez.container.size lower than this value. if this is the case then you will see your task container get launched with the yarn.scheduler.minimum-allocation-mb. the best practice is to set hive.tez.container.size to be the same as or a small multiple (1 or 2 times that) of YARN container size yarn.scheduler.minimum-allocation-mb but never more than yarn.scheduler.maximum-allocation-mb. You want to have headroom for multiple containers to be spun up.
... View more
12-19-2016
12:40 PM
4 Kudos
During debugging a problem with delete topic,I dig into Kafka code to know how delete command works, this the sequence of event occurred during command execution 1. TopicCommand issues topic deletion /usr/hdp/current/kafka-broker/bin/kafka-run-class.sh kafka.admin.TopicCommand --zookeeper rkk3.hdp.local:2181 --delete --topic sample 2. which create a new admin path /admin/delete_topics/<topic> 3. The controller listens for child changes on /admin/delete_topic and starts topic deletion for the respective topics 4. The controller has a background thread that handles topic deletion. A topic's deletion can be started only by the onPartitionDeletion callback on the controller. 5. Once DeleteTopicsThread invoked it looks for topicsToBeDeleted and for each topic it deregister partition change listener on the deleted topic, This is to prevent the partition change listener firing before the new topic listener when a deleted topic gets auto created. 6. Controller will remove this replica from the state machine as well as its partition assignment cache. 7. Deletes all topic state from the controllerContext as well as from zookeeper and finally delete /brokers/topics/<topic> path. 8. onTopicDeletion is callback by the DeleteTopicThread,This lets each broker know that this topic is being deleted and can be removed from their caches.
... View more
Labels:
12-19-2016
11:22 AM
1 Kudo
could you please try query after increasing innodb_lock_wait_timeout to 600, restart of mysql db required in this case.
... View more
12-19-2016
09:17 AM
@sathish jeganathanthere is no need to specify advertised listener,what hdp version you are currently running with? can you try to set following setting and see if it helps.make both listeners and advartised.listeners same. listeners=SASL_PLAINTEXT://localhost:6667 advartised.listeners=SASL_PLAINTEXT://localhost:6667
... View more
12-19-2016
07:41 AM
@Rajesh AJ looks you added sources jar not the jar with compiled classes, add jar from the following location add jar /usr/hdp/current/hive-client/lib/commons-httpclient-3.0.1.jar
... View more
12-19-2016
07:08 AM
@sathish jeganathan any luck with the above mentioned settings.
... View more
12-19-2016
07:07 AM
3 Kudos
@Rajesh AJcould you please add the following jar in hive cli add jar /usr/hdp/current/hive-client/lib/commons-httpclient-3.0.1.jar if you are using hiveserver2 then add this jar into hive_aux_jars and restart hiveserver2
... View more
12-19-2016
06:06 AM
@sathish jeganathan could you please try following steps 1. open ambari, open kafka configuration 2. update listeners=SASL_PLAINTEXT://localhost:6667 3.remove advartised.listeners and save configuration 4. restart kafka broker and see if helps
... View more