Closed Bug 865301 Opened 12 years ago Closed 12 years ago

ES on jenkins is sick once again

Categories

(Infrastructure & Operations Graveyard :: WebOps: Other, task, P1)

All
Other

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: rrosario, Assigned: bburton)

References

Details

+++ This bug was initially created as a clone of Bug #859578 +++ For the past few days, all of our tests that depend on ES have been randomly failing and the problem seems to be getting worse. Short term fix: restart ES please? Thanks!
Restarted [bburton@jenkins1.dmz.phx1 ~]$ sudo service elasticsearch stop Stopping elasticsearch: elasticsearch: stopped [ OK ] [bburton@jenkins1.dmz.phx1 ~]$ sudo service elasticsearch start Starting elasticsearch: elasticsearch: started [ OK ]
Assignee: server-ops-webops → bburton
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Now that bug 798155 is resolved, we have an ES 0.20.x instance available for Jenkins. Use the server name 'jenkins-es20' and port 9200 to use the new instance. The exist 0.17.x instance on localhost will stay running for another month or two though.
I changed our scripts/build.sh script to use the new ES cluster in https://github.com/mozilla/kitsune/commit/cada25853f78fd1494dbbf1aa4671e196f46f9b9 I'm so excited that I'm doing this at 9:20pm on a friday night.
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.