Member since
07-30-2018
60
Posts
14
Kudos Received
5
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 1933 | 06-20-2019 10:14 AM | |
| 17660 | 06-11-2019 07:04 AM | |
| 2312 | 03-05-2019 07:25 AM | |
| 4237 | 01-03-2019 10:42 AM |
06-20-2019
10:14 AM
Hi, Yes, We can enforce a job to run in a particular queue based on user using placement policy. We can define a secondary group for each user. Whenever the user submits a job will land on the secondary group queue. reference Link: https://blog.cloudera.com/blog/2016/06/untangling-apache-hadoop-yarn-part-4-fair-scheduler-queue-basics/ Thanks Jerry
... View more
06-11-2019
07:04 AM
Hi, Please use the below steps if your cluster is unsecure. kafka-topics --create --zookeeper <zk host>:2181 --replication-factor 3 --partitions 1 --topic Testmessage Run a Kafka console producer: $ kafka-console-producer --broker-list <broker hostnome>:9092 --topic Testmessage Run a Kafka console consumer: $ kafka-console-consumer --new-consumer --topic Testmessage --from-beginning --bootstrap-server <broker hostnome>:9092 Thanks Jerry
... View more
06-10-2019
04:33 AM
Hi, From the logs, It seems its unable to find the broker "Connection to node -1 (localhost/127.0.0.1:9092) could not be established" Make sure you have broker running in the node and listening to 9092 Also try adding the fully qualified name or IP instead of localhost Thanks Jerry
... View more
04-22-2019
01:45 AM
Hi, Its showing that it is running in unsupported version. Could you let us know the below version Kafka, CDH, System Java version. 'major.minor version 52.0' Will occur if you are running the application in JAVA version which is less than 1.8
... View more
04-16-2019
08:32 AM
2 Kudos
Hi, Impala query usually faster on 2nd time than 1st attempt of same query. This is because of OS cache, Which will keep the files in memory and reuse it. It is OS level feature and not specific to Impala. For further performance improvement, there is a concept of "HDFS caching" which is utilized by Impala. HDFS Caching helps further to improve the speed of query results Reference Link below: https://www.cloudera.com/documentation/enterprise/5-8-x/topics/impala_perf_hdfs_caching.html Thanks Jerry
... View more
03-05-2019
07:25 AM
Hi Sandeep, It seems the data has been imported as the count is same. But sometimes the datatype might be different between MS-SQL and Hive tables which result in NULL values. Let's try to check the datatype between the tables and also share the sqoop command for further check Thanks Jerry
... View more
01-29-2019
06:47 AM
Hi Tulasi, Could you check the value of this property Container Executor Group from the file "container-executor.cfg" file and cross check with CM configuration Thanks Jerry
... View more
01-28-2019
10:33 AM
Hi Tulasi, Could you please verify the "container-executor.group" are same on both from Cloudera manager (Yarn->Configuration->Container Executor Group) and /etc/hadoop/conf.cloudera.yarn/container-executor.cfg (from Node manager host) Let us know if you have questions Thanks Jerry
... View more
01-03-2019
10:42 AM
1 Kudo
Hi, When importing an empty table from Teradata to HDFS via Sqoop using the --table option, We are getting the below exception com.teradata.connector.common.exception.ConnectorException: Input source table is empty Its a bug from teradata end and the fix is yet to be released. Until the fix is available, We recommend using sqoop import --query as a workaround instead of --table Hope it helps. Let us know if you have any questions Thanks Jerry
... View more