Closed
Bug 1162604
Opened 9 years ago
Closed 9 years ago
Index nothing but mozilla-inbound
Categories
(Testing Graveyard :: ActiveData, defect)
Testing Graveyard
ActiveData
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: ekyle, Assigned: ekyle)
References
Details
The weak ES cluster can not handle the number of records. Update the indexing routines to only insert `mozilla-inbound` and 10% of the other branches. The 10% is to remind query writers to filter by branch.
Assignee | ||
Comment 1•9 years ago
|
||
Other branches set to 1% https://github.com/klahnakoski/TestLog-ETL/commit/64106a1634735aec3779c4b67e258af87e2d5a04
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Comment 2•9 years ago
|
||
I guess it depends on what type of problems we're trying to solve, but if we had to choose a single branch to index, I'd prefer mozilla-central. Because: 1) Inbound is only one of 3+ integration branches. So it will miss changes incoming from fx-team or b2g-inbound until central is merged back in. 2) Inbound has no guarantee of stability, every push could potentially be backed out and cause anomalies in the data. Alternatively, would it be possible to index both inbound and central? Central has <10 pushes per day, so shouldn't be *too* much extra load.
Assignee | ||
Comment 3•9 years ago
|
||
I will include mozilla-central. It will be days before it is backfilled.
Updated•3 years ago
|
Product: Testing → Testing Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•