Hello, Our team has successfully set up a XDC configuration across 2 datacenters. The basic flow is working as expected.
However, it appears that Time Routed Aliases may not work with XDC Solr 9.10.1. After creating the same TRA (router.start to 2020-01-01T00:00:00Z and interval to 1 year) in the SolrClouds in both data centers. We index to the primary alias with 2025 messages and then 2020 collections up to 2025 collection (under the TRA) are created and the 2025 collection is populated with docs, Kafka picks up the data and mirrors it to the secondary, and the same happens on the secondary. Good so far. When 2026 data is indexed to the primary SolrCloud it is indexed successfully, but the mirroring fails to the secondary SolrCloud. The xdc-manager running in the secondary DC gets the message to index, but there is no 2026 collection (associated with the TRA) that the document can be indexed to. With XDC working at the collection level, it makes sense it is trying to mirror to the collection and not to the TRA. However, this does not allow for TRA mirroring in XDC. Any ideas/feedback? We wondered about having the xdc-manager, on this error, fire a generic message to the TRA associated with the tra collection, to trigger collection creation in the secondary. Or possibly on the producer side, if the collection is part of a TRA, to change the mirroring target to be the TRA rather than the TRA collection. Thanks, Matt
