|
1 | 1 | # dataone-indexer Release Notes |
2 | 2 |
|
| 3 | +> [!NOTE] |
| 4 | +> The Helm chart now assumes you have the [RabbitMQ Cluster Operator](https://www.rabbitmq.com/kubernetes/operator/operator-overview) pre-installed on your Kubernetes cluster. Alternatively, it can be configured to use your existing RabbitMQ instance - see [the README file](./README.md#deploying-the-application-via-helm) for details. |
| 5 | +
|
| 6 | + |
| 7 | +### helm chart version 2.0.1 |
| 8 | + |
| 9 | +### Release date: 2026-02-09 |
| 10 | + |
| 11 | +This is a patch release to fix a bug with the new RabbitMQ Cluster Operator-based deployment introduced in version 2.0.0, and to refine some performance settings for RabbitMQ and Solr. |
| 12 | +- Bug fix: Setting `rabbitmq.enabled: false` in the Helm values.yaml did not disable the installation of the RabbitMQ operator as expected ([Issue #308](https://github.com/DataONEorg/dataone-indexer/issues/308)) |
| 13 | + |
| 14 | +- Indexing Performance - Configuration Changes for Index Worker and Solr ([Issue #319](https://github.com/DataONEorg/dataone-indexer/issues/319): |
| 15 | + - Indexer is now configured to perform automatic Solr commits instead of forcing a hard commit after every Solr update |
| 16 | + - Auto-commit time periods can be overridden using `solr.extraEnvVars` to set `SOLR_OPTS` |
| 17 | + to `"-Dsolr.autoCommit.maxTime=<hardPeriod> -Dsolr.autoSoftCommit.maxTime=<softPeriod>"`. Default values are 1 second for auto soft commits, and 120 seconds for auto hard commits. |
| 18 | + - Forced commits per update can be controlled using `commitPerUpdate.hardCommit` and `commitPerUpdate.softCommit`. Both default to `false`. |
| 19 | + - See https://solr.apache.org/guide/solr/latest/configuration-guide/commits-transaction-logs.html for details |
| 20 | + - `solr.javaMem` changed from `"-Xms512m -Xmx2g"` to `"-XX:MaxRAMPercentage=50"` |
| 21 | + |
| 22 | +- RabbitMQ Changes ([Issue #311])(https://github.com/DataONEorg/dataone-indexer/issues/311)) |
| 23 | + - Add `rabbitmq.autoPodAntiAffinity` to spread RabbitMQ pods across nodes - recommended for production installations with multiple replicas, to increase availability. |
| 24 | + - Anti-affinity can be "required" or "preferred", and weigth is configurable |
| 25 | + - Can be overridden disabled, or completely overridden using new `rabbitmq.affinity` section |
| 26 | + - `rabbitmq.additionalConfig`: removed `additionalConfig: disk_free_limit.relative: "1.0"` and replaced with `disk_free_limit.absolute: 1500MB` |
| 27 | + - See: https://www.rabbitmq.com/docs/production-checklist#resource-limits-disk-space |
| 28 | + |
| 29 | + |
3 | 30 | ## dataone-indexer version 3.2.0 & helm chart version 2.0.0 |
4 | 31 |
|
5 | 32 | ### Release date: 2025-12-02 |
|
0 commit comments