Member since
01-19-2017
3681
Posts
633
Kudos Received
372
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 1602 | 06-04-2025 11:36 PM | |
| 2071 | 03-23-2025 05:23 AM | |
| 981 | 03-17-2025 10:18 AM | |
| 3732 | 03-05-2025 01:34 PM | |
| 2565 | 03-03-2025 01:09 PM |
05-08-2019
09:18 PM
@Erkan ŞİRİN Can you add these values in your mapred.xml get the values of mapreduce.job.ubertask.maxbytes from hdfs-site.xml mapreduce.job.ubertask.enable = true
mapreduce.job.ubertask.maxmaps = 1
mapreduce.job.ubertask.maxreduces = 1
mapreduce.job.ubertask.maxbytes = {get value from hdfs dfs.block.size parameter in hdfs-site.xm Then restart the YARN and MR and relaunch the job
... View more
05-04-2019
07:23 AM
1 Kudo
@duong tuan anh I can see hiveServer2 also has an issue can you resolve that or what is the problem. It's the TSv2 which is not starting can you share specifically those logs? Change you run the below snippets $ hdfs dfs -chown -R yarn:hadoop /ats Finally $ hdfs dfs -chown -R yarn-ats:hdfs /atsv2/hbase Restart the services and revert HTH
... View more
05-03-2019
11:05 AM
@duong tuan anh Any updates
... View more
05-03-2019
08:03 AM
1 Kudo
@duong tuan anh Indeed the files are huge can you do a quick solution I saw after reading your logs, Caused by: org.apache.hadoop.security.AccessControlException As the root user switch to hdfs # su - hdfs Change ownership of the mapred directory $ hdfs dfs -chown -R mapred:hadoop /mr-history That should resolve the problem. Keep me posted
... View more
05-03-2019
12:46 AM
1 Kudo
@duong tuan anh Can you also attach the below recent logs hadoop-yarn-resourcemanager-xxxx.log
hadoop-yarn-nodemanager-xxxx.log
hadoop-yarn-root-registrydns-xxxx.log
hbase-yarn-ats-master-xxxx.log Thank you
... View more
05-02-2019
08:56 AM
@duong tuan anh Can you share the YARN/MR logs?
... View more
04-30-2019
03:16 PM
@Michael Bronson Any updates?
... View more
04-30-2019
11:04 AM
@Naveenraj Devadoss What was the solution? Did you update the network config in /etc/host?
... View more
04-29-2019
07:59 PM
@Erkan ŞİRİN Sorry, could get back much earlier ... It won't cost you to try so that we have that eliminated among the possible solutions "Ensure that you have called .close() on any active streaming result sets before attempting more queries. " corresponds to that!
... View more