VirtualFlyBrain/geppetto-vfb: v2.2.11.4 — data spread across the ingress nodes

Le résumé fourni par la source

Mesh and data files used to be fetched from a single round-robin name, so every session queued on whichever host it happened to resolve, and one failed call fell straight through to the server rather than being retried. The ingress nodes are now named directly — buttermilk, parsley, sourcream, chive, mayo, dill and cayenne, each with its own 1Gb link — and the node serving a file is chosen from the file's path. A page loading several meshes now takes them from several nodes at once, while each file stays on one node so the browser cache still hits on a revisit. Loading nine meshes on v2-dev drew them from four nodes, where previously all nine came from one. A node that cannot be reached drops out for that session and the published name serves instead, so this degrades to the previous behaviour rather than failing. Each retry moves to a different node. Data calls are now retried four times with backoff before any fallback, and a failure reports why it failed and which call it was, instead of only how long it took. The term's query list and the template ROI tree were still giving up after one attempt and now retry too. Requires geppetto-client VFBv2.4.5.3. The node hostnames are covered by the reissued certificate; vfbk8s10-12 are reserved but not yet in use.

Ce résumé expose les affirmations des auteurs. BNTIC ne l’interprète pas comme une validation indépendante des résultats.