Closed
Bug 1255457
Opened 9 years ago
Closed 9 years ago
Presto connection closed to Hive
Categories
(Cloud Services Graveyard :: Metrics: Pipeline, defect, P1)
Cloud Services Graveyard
Metrics: Pipeline
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: rvitillo, Assigned: whd)
References
Details
(Whiteboard: [SvcOps])
See [1] for the error and a possible solution. Not sure we started experiencing this issue only now.
[1] https://forums.aws.amazon.com/thread.jspa?threadID=220302
Reporter | ||
Updated•9 years ago
|
Flags: needinfo?(whd)
Assignee | ||
Comment 1•9 years ago
|
||
We're testing the fix outlined in comment #1. For our flavor of Presto/Hive the classpaths are such that:
ln -s /usr/lib/presto/plugin/mysql/mysql-connector-java-5.1.35.jar /usr/lib/hadoop/lib/mysql-connector-java.jar
DTRT. We can make this fix permanent using techniques in https://docs.aws.amazon.com/ElasticMapReduce/latest/DeveloperGuide/emr-dev-create-metastore-outside.html, but at that point we should probably go whole hog and make the related change of storing this in a proper RDS instance.
A workaround we discovered is to run hive periodically.
Flags: needinfo?(whd)
Comment 2•9 years ago
|
||
I was running a non-trivial amount of queries through Redash over the weekend (3/12 and 3/13) and did not hit the exception. Seems like the workaround is working.
Updated•9 years ago
|
Assignee: nobody → whd
Points: --- → 3
Priority: -- → P1
Comment 3•9 years ago
|
||
back to a P2 - :whd is on ops related tasks for the next while. will prioritize when when he becomes available again.
Priority: P1 → P2
Updated•9 years ago
|
Whiteboard: [SvcOps]
Reporter | ||
Updated•9 years ago
|
Severity: normal → major
Priority: P2 → P1
Assignee | ||
Comment 4•9 years ago
|
||
This seems to have been fixed by upgrading to Hive 1.2.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•