Closed
Bug 1311781
Opened 9 years ago
Closed 9 years ago
Increase ATMO node limit from 20 to 30
Categories
(Cloud Services Graveyard :: Metrics: Pipeline, defect)
Cloud Services Graveyard
Metrics: Pipeline
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bmiroglio, Unassigned)
References
Details
Attachments
(1 file)
I'm trying to generate a fresh sample of the Longitudinal dataset, however this job requires 30 nodes. This is a one time job as an effort to augment data for a modeling project. The segment of profiles we are interested in is very exclusive, so having a second sample to union with an existing dataset would be quite helpful :).
|
||
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
|
|
||
Updated•9 years ago
|
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
|
|
||
Comment 2•9 years ago
|
||
Re-opened after finding out that it's not in fact a duplicate of bug 1311475
|
||
Comment 3•9 years ago
|
||
|
|
||
Comment 4•9 years ago
|
||
This is now fixed in atmo v2 staging and will deployed soon to prod.
Status: REOPENED → RESOLVED
Closed: 9 years ago → 9 years ago
Resolution: --- → FIXED
|
||
Updated•7 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
•