Member since
05-19-2016
25
Posts
3
Kudos Received
1
Solution
My Accepted Solutions
Title | Views | Posted |
---|---|---|
7156 | 12-02-2016 08:20 AM |
06-29-2017
06:19 PM
Check /tmp/hive for hive log and you will see the error stacktrace there.
... View more
06-29-2017
06:05 PM
There is no way to run multiple DAG concurrently in single Tez AM, and this is Tez limitation. But HiveServer2 support multiple concurrent queries with multiple Tez AM.
... View more
03-19-2017
06:31 AM
It looks like Tez AM container cannot be scheduled. Typically this is caused by not enough resource. Please check your cluster capacity to ensure you have enough resource for Tez container.
... View more
12-22-2016
06:45 PM
Increasing timeout cannot guarantee tez dags to be loaded. You may want to find why tez dags won't load also.
... View more
12-09-2016
11:44 PM
This is not the app log. Please use "yarn log --applicationId <appId>" to retrieve the app log.
... View more
12-03-2016
12:06 AM
Map vertex get killed because Reduce vertex failed. Any log for reduce vertex?
... View more
12-03-2016
12:02 AM
Your resource is limited. To solve the problem, either you allocate more resource or just request ask fro resource.
... View more
12-02-2016
07:04 PM
Never mind about cluster size. I saw you are using sandbox. Probably job cannot be started because there is not enough resource. You can try allocate more memory for VM or decrease tez container size.
... View more
12-02-2016
06:22 PM
Job is not started at all. Please share more info for debugging(cluster size, query, data size, hive log, etc)
... View more
12-02-2016
08:51 AM
Typically tez.runtime.framework.local.dirs isn't used by user, and it's only used internally by Tez. Its value comes from YARN local dirs configuration through environment variable for containers. There are several ways for LocalDirAllocator to find no valid local dir: 1. disk/dir is full; 2. disk/dir is not writable; 3. local dirs settings is not correct. Since mapreduce based jobs work fine for you, I assume there is not issue about disk being full or unwritable. You should check whether env var LOCAL_DIRS is correct by looking at container launching script.
... View more
12-02-2016
08:20 AM
Your settings are mapreduce settings which may be not recognized by tez. Try setting tez config 'tez.task.resource.memory.mb' and 'tez.task.launch.cmd-opts' corresppondingly.
... View more
11-03-2016
04:52 AM
You can set hive/tez to use a specified queue. For tez, the configuration is 'tez.queu.name'. Regarding to queue capacity settings, please refer to this link.
... View more
09-27-2016
12:37 AM
Looks a bug in either Hive or Tez. Would you mind filing a jira in apache and uploading logs there?
... View more
08-23-2016
05:57 AM
Thanks for the performance evaluation! Any explanation why Databricks CSV library's performance performs well?
... View more
07-07-2016
09:14 PM
This log is incomplete and doesn't help. Would you mind sharing the hive log when you trigger the same error? Your can share it via pastebin or collabedit.
... View more