Closed Bug 1319894 Opened 8 years ago Closed 8 years ago

ensure consistent jvm memory configuration across nodes

Categories

(Socorro :: Infra, task)

Product:
Socorro
Component:
Infra
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: lonnen, Assigned: miles)

References

Details

One of our ES nodes is not configured like the others. For specific id, see https://docs.google.com/document/d/14Ffc7_dJM_UAVAftcP_i6dqx7nU7-wmGMzWO8iCmuos/edit?ts=5835d9a8
Assignee: nobody → miles
Blocks: 1322629
In performing a rolling restart of the production cluster I dumped the node settings of the cluster, and confirmed that the node in question had a "jvm.mem.heap_max_in_bytes" double that of the others. Restarting the elasticsearch process resolved the issue for that node.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.