Since allocators is a limited resource in Blazegraph, we should monitor them so that we know anything is wrong before things start breaking. With this in mind, we should create a monitoring measure for number of free allocators. We can call status?dumpJournal on Blazegraph, parse the response, sum up all used allocators and see how much is left from 256k available.
Description
Description
Details
Details
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Smalyshev | T213210 WDQS is hitting allocator limit on Blazegraph | |||
| Resolved | Smalyshev | T213372 Create monitoring of allocators |
Event Timeline
Comment Actions
Change 485135 had a related patch set uploaded (by Smalyshev; owner: Smalyshev):
[operations/puppet@production] Add allocator metrics export for Blazegraph
Comment Actions
Change 485135 merged by Gehel:
[operations/puppet@production] Add allocator metrics export for Blazegraph
Comment Actions
Change 486356 had a related patch set uploaded (by Gehel; owner: Gehel):
[operations/puppet@production] wdqs: add icinga check of free blazegraph allocators
Comment Actions
Change 486356 merged by Gehel:
[operations/puppet@production] wdqs: add icinga check of free blazegraph allocators