Member since
10-01-2016
156
Posts
8
Kudos Received
6
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
8311 | 04-04-2019 09:41 PM | |
3175 | 06-04-2018 08:34 AM | |
1481 | 05-23-2018 01:03 PM | |
2993 | 05-21-2018 07:12 AM | |
1842 | 05-08-2018 10:48 AM |
10-12-2019
10:10 PM
3 Kudos
Go to Ambari -> Hive -> Configs -> Advanced -> Custom hive-site Click Add Property Insert followings into the opening window: hive.security.authorization.sqlstd.confwhitelist.append=mapred.compress.map.output After saving, restart hive services. Then connect to beeline and set your parameter. I experienced a similar problem for mapreduce.job.reduces parameter and it worked.
... View more
10-05-2019
04:24 AM
@erkansirin78 Great !! it worked out for you, If you found this answer addressed your question, please take a moment to log in and click the thumbs up button. That would be a great help to Cloudera Community to find the solution quickly for these kinds of errors and mark it as a solution
... View more
07-31-2019
06:46 AM
Hi @Shu thank you. Adding spark-yarn_x.x.jar to maven repository solved the problem. But I have come across other errors. Anyway in here the problem was parsing the yarn and it is solved.
... View more
08-27-2018
06:36 PM
Hi again @Felix Albani I use Intellij IDEA. I put the arguments into run -> edit configurations -> program arguments as below. But it didn't work.
... View more
07-17-2018
02:03 PM
Excellent - glad that's working! There is a patch being tested for this issue here, too: https://issues.apache.org/jira/browse/ZEPPELIN-3128
... View more
07-16-2018
06:23 AM
Thank you @rguruvannagari I just enabled SolrCloud and restarted. I don't see audit error anymore.
... View more
07-13-2018
12:23 PM
There are a few possible causes for this, but with only one message in the queue and a fairly short (which I'm reading here as low-impact) job, my first bet would be that the permissions are not set up in Ranger for the Hive user to be able to write to the Atlas Kafka topic. (https://community.hortonworks.com/questions/60564/atlas-api-times-out-on-entity-creation.html)
... View more
07-19-2018
01:49 PM
A week later I got similar problem again. When I closed some other services Atlas could be able to start. I think unsufficient resourses prevent Atlas to start.
... View more
07-16-2018
06:44 AM
I tried sqoop and get following error bu import is successfull ERROR security.InMemoryJAASConfiguration: Unable to add JAAS configuration for client [KafkaClient] as it is missing param [atlas.jaas.KafkaClient.loginModuleName]. Skipping JAAS config for [KafkaClient] and org.apache.atlas.notification.NotificationException: java.util.concurrent.ExecutionException: org.apache.kafka.common.errors.TimeoutException: Expiring 1 record(s) for ATLAS_HOOK-0 du e to 30075 ms has passed since batch creation plus linger time
at org.apache.atlas.kafka.KafkaNotification.sendInternalToProducer(KafkaNotification.java:239)
at org.apache.atlas.kafka.KafkaNotification.sendInternal(KafkaNotification.java:212)
at org.apache.atlas.notification.AbstractNotification.send(AbstractNotification.java:114)
at org.apache.atlas.hook.AtlasHook.notifyEntitiesInternal(AtlasHook.java:143)
at org.apache.atlas.hook.AtlasHook.notifyEntities(AtlasHook.java:128)
at org.apache.atlas.sqoop.hook.SqoopHook.publish(SqoopHook.java:190)
at org.apache.atlas.sqoop.hook.SqoopHook.publish(SqoopHook.java:51)
at org.apache.sqoop.mapreduce.PublishJobData.publishJobData(PublishJobData.java:52)
at org.apache.sqoop.mapreduce.ImportJobBase.runImport(ImportJobBase.java:284)
at org.apache.sqoop.manager.SqlManager.importQuery(SqlManager.java:748)
at org.apache.sqoop.tool.ImportTool.importTable(ImportTool.java:509)
at org.apache.sqoop.tool.ImportTool.run(ImportTool.java:615)
at org.apache.sqoop.Sqoop.run(Sqoop.java:147)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
at org.apache.sqoop.Sqoop.runSqoop(Sqoop.java:183)
at org.apache.sqoop.Sqoop.runTool(Sqoop.java:225)
at org.apache.sqoop.Sqoop.runTool(Sqoop.java:234)
at org.apache.sqoop.Sqoop.main(Sqoop.java:243)
Caused by: java.util.concurrent.ExecutionException: org.apache.kafka.common.errors.TimeoutException: Expiring 1 record(s) for ATLAS_HOOK-0 due to 30075 ms has passed since batch creat ion plus linger time
at org.apache.kafka.clients.producer.internals.FutureRecordMetadata.valueOrError(FutureRecordMetadata.java:65)
at org.apache.kafka.clients.producer.internals.FutureRecordMetadata.get(FutureRecordMetadata.java:52)
at org.apache.kafka.clients.producer.internals.FutureRecordMetadata.get(FutureRecordMetadata.java:25)
at org.apache.atlas.kafka.KafkaNotification.sendInternalToProducer(KafkaNotification.java:230)
... 17 more
Caused by: org.apache.kafka.common.errors.TimeoutException: Expiring 1 record(s) for ATLAS_HOOK-0 due to 30075 ms has passed since batch creation plus linger time
... View more