February 19, 2026- We are rolling out BOINC server release 1.6.1 in production, as we successfully re-based our BOINC server build onto recently released upstream v1.6.1 and cherry-picked changes from legacy and new WCG development, passing all tests and adding new ones for WCG-specific customizations. The scheduler, transitioner, and feeder will now run alongside the create_work daemons, Redpanda brokers, file_upload_handlers, and combined validator_assimilator daemons on the BOINC backend cluster and serve only the node local partition, handling only BOINC client requests routed to that server by the load balancer.
- We are migrating the SQLite instances across the BOINC backend nodes to a Citus-Data v14.0 PostgreSQL database cluster, completing our transition to a horizontally scalable architecture for the BOINC backend via the Redpanda cluster, PostgreSQL database cluster, and our changes to enforce end-to-end data locality in workunit processing within individual partitions by changing signed URL generation to include buckets owned by a specific partition/node on the backend, and providing the load balancer a mapping of buckets to the correct backend node. While we have had bugs in multiple components as we made changes to the backend, all components now consistently apply the same hashing function to a given workunit ID to achieve correct routing, and as we loop the database and scheduler into this design we expect to finally be able to communicate the value of the new architecture in results as we restart ARP1, and finally rollout MAM1 and seek to backport the MAM1 application to the MCM1 project, for BOINC clients running on devices that can handle it. We will not close the path for less powerful devices to contribute, only add the path for more powerful devices to contribute more than they currently can.
- MAM1 v7.0.8 for Linux and Windows, and ARP1 will release as soon as the BOINC server v1.6.1 and distributed PostgreSQL database cluster rollouts are complete, we will then also enable stats export. We will be able to gather the remaining backlog for validation from the postgres cluster more easily than the currently bogged down legacy BOINC database, and perform the final phase of validation backlog reconciliation.
- Results page under My contribution, as correctly guessed in the forums, the botched rollout of the new results page was a direct attempt to reduce load on the BOINC database from the APIs now that result tables have grown so large, while attempting to preserve the ability of volunteers to inspect their results and confirm for themselves the validation state of their PV jails, which we have finally made progress on. After restoring basic functionality of the new server-side in-memory caching approach, we left several issues unresolved and proceeded to work on the above items. A fix is incoming to enable downloading all results instead of the 500 currently displayed, and to fix the conditions that cause the summary stats to show more results in the numerator than in the denominator, and to address the behaviour of filtering among others.
- Fixed Apache mod-security rules blocking Team Challenge and Invite to Challenge functionality, and we suspect multiple other 403 forbidden issues to be related to the upgrades to the Apache webserver and HAProxy load balancer at the start of the transition. More fixes are incoming for the website, once we have completed the rollout of the final pieces of our new horizontally scalable architecture, removing the BOINC database as a single point of contention, and launching all remaining applications as described above.
bron:
Jurisica Lab
Hebben jullie even wat te lezen
[World Community Grid] hitparade van 17 februari
Total flushers: 40
More...
More...
More...
More...
Links
World Community Grid homepage
World Community Grid stats van alle Teams
World Community Grid stats van DPC
World Community Grid stats van DPC voor BOINC clients
Bron DPCH
Kuuke's Sterrenbeelden | 英俊的兔子