Skip to content

Changelog

Gateway changes

Changes to how the gateway selects, measures and pays indexers, newest first.

Gateway releaseVersion requirementsIndexer selectionQoS measurement

Gateway follows upstream v27.8.0, and Graph Node must report its version

The GraphOps Subgraph gateway now runs code derived from upstream release v27.8.0. Every change GraphOps contributed upstream has been merged and ships in that release: #1221 to #1227, #1229 and #1230.

An indexer whose Graph Node doesn't report its version is no longer selected until it reports one (#1230). Before, the Graph Node minimum applied only when a version was reported. An indexer below either minimum is still not selected.

The gateway publishes its version and the minimum indexer-service and Graph Node versions it requires at /version (#1229). Constraints shows them.

Query durations longer than 65 seconds are now reported in full instead of wrapping around to a much shorter value (#1226).

What to do: Check that indexer-service /status answers Graph Node's { version { version } } query, and that both versions meet the minimums on Constraints.

Gateway releaseIndexer selectionQoS measurement

Selection follows failing indexers closely, and time behind chain head follows indexing

An indexer whose requests all fail drops out of selection and stays out until it answers successfully again. Only successful responses count toward an indexer's latency. Indexers that answer successfully are scored as before.

Time behind chain head now tracks indexing progress more closely, especially for indexers that are queried infrequently. An indexer whose reported block stops advancing is counted as behind until it moves again.

If /status stops answering, the gateway keeps using the indexer's last report for a short time, then treats the indexer as having no indexing status until /status answers again.

What to do: Keep /status answering and fix failing requests promptly: an indexer returns to selection as soon as it answers successfully again.

Gateway releaseQoS measurement

GraphOps Subgraph gateway released

The GraphOps Subgraph gateway is publicly available. It runs code derived from upstream gateway commit 88ea417, which follows release v27.7.1 and includes fixes GraphOps contributed upstream (#1221 to #1225 and #1227).

They fix a gateway crash on a GraphQL error message with a multibyte character at its 256-byte limit (#1223), query reports merging after a failed delivery (#1222), and the gateway's query-duration and request-count metrics (#1225, #1227).