Closed
Bug 1478093
Opened 7 years ago
Closed 7 years ago
Deploy emr-bootstrap-spark to pick up telemetry-spark-packages-assembly
Categories
(Data Platform and Tools Graveyard :: Operations, enhancement)
Data Platform and Tools Graveyard
Operations
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: klukas, Assigned: klukas)
References
Details
We previously deployed and rolled back a change [0] to make spark-hyperloglog available by default. We've now merged a new approach to spark packages into emr-spark-bootstrap [1] and are ready for a new deploy with that code.
Before merging, I tested on a variety of cluster sizes and EMR versions and found that spark-hyperloglog was available (so the new functionality works) and that I was able to run the entire Telemetry Hello World notebook (which lends confidence that this will not break existing workflows).
[0] https://bugzilla.mozilla.org/show_bug.cgi?id=1474347
[1] https://github.com/mozilla/emr-bootstrap-spark/pull/407#issuecomment-407488823
Comment 1•7 years ago
|
||
I'm at a conference this week but per https://bugzilla.mozilla.org/show_bug.cgi?id=1474347#c18 it looks like you know how to deploy emr-bootstrap-spark. Deploying to production is documented at https://github.com/mozilla/emr-bootstrap-spark/#deploy-to-aws-via-ansible and you have the requisite access to do so. Since ops isn't really providing anything of value here I suggest you deploy this to stage/prod yourself and verify it works as expected.
Assignee | ||
Comment 2•7 years ago
|
||
That's a totally reasonable point. I will go ahead and move this forward.
Assignee | ||
Updated•7 years ago
|
Assignee: nobody → jklukas
Assignee | ||
Comment 3•7 years ago
|
||
Deployed to stage and all looks good on a test ATMO cluster I spun up. Deploying to prod now.
Assignee | ||
Comment 4•7 years ago
|
||
Deployed to prod and looks good there too. Resolving.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Updated•2 years ago
|
Product: Data Platform and Tools → Data Platform and Tools Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•