[release][CI] long_running_impala failed
See original GitHub issueWhat happened + What you expected to happen
Looks like OOM issue related.
Traceback (most recent call last):
File "workloads/impala.py", line 61, in <module>
callbacks=[ProgressCallback()],
File "/home/ray/anaconda3/lib/python3.7/site-packages/ray/tune/tune.py", line 877, in run_experiments
callbacks=callbacks,
File "/home/ray/anaconda3/lib/python3.7/site-packages/ray/tune/tune.py", line 771, in run
raise TuneError("Trials did not complete", incomplete_trials)
ray.tune.error.TuneError: ('Trials did not complete', [IMPALA_CartPole-v1_0ee4f_00000])
Versions / Dependencies
NA
Reproduction script
NA
Issue Severity
No response
Issue Analytics
- State:
- Created a year ago
- Comments:12 (12 by maintainers)
Top Results From Across the Web
How to kill Long running impala queries - Cloudera Community
Solved: Hi, Am trying to kill long running query from CM. But the opraion failed with internal error. I got - 30966.
Read more >[release/rllib] long running impala fails (deadline exceeded)
[release/rllib] long running impala fails (deadline exceeded) #15224 ... Loading environment football failed: No module named 'gfootball' ...
Read more >Trying to Cancel Long Running Impala Queries Fails with ...
When attempting to cancel an Impala query through the Cloudera Manager Web Interface, an internal error is reported and the query is not ......
Read more >Fixed Issues in Apache Impala
CREATE TABLE or ALTER TABLE statements could fail with metastore database errors due to length limits on the SERDEPROPERTIES and TBLPROPERTIES clauses. (The ......
Read more >Amazon EMR FAQs - Big Data Platform - Amazon Web Services
FAILED – The step failed while running. Launching a cluster. Q: How can I launch a cluster? You can launch a cluster through...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
^ agent mem usage is 169MB after 23h run. So I think it can be closed
The fix PR was merged after this date (it is merged on 20th).