Hello Solr World, I'm a firefighter, brought in to help nurse a Solr Cloud system back to life until it can be replaced. It's running Solr 6.5, and a data item (key) field exceeded what will fit in a signed 32-bit collection field a while ago.
I've been able to make a new collection with 64-bit fields, and new data is being inserted, and an alias created using: http://shard-01:8983/solr/admin/collections?action=CREATEALIAS&name=alias&collections=collection2,collection1 Works as hoped/expected for both queries and inserts. BUT, the alias definition does not persist between restarts. I haven't spotted any newly written (aliases.json?) file(s) created on any of the shards, or the zookeper system (all of the shards and zookeeper are running in Docker containers). It's entirely possible this is due to permission issues (but no errors appeared in the log file on the shard where I issued the command). This is for a non-profit/academic research organization with a tight budget (and I'm helping them recover from an extended period of things not working at all), so "doing it right", upgrading etc may not be in the cards, and I'm hoping I just need to create an aliases.json file of the right format, in the right location. I tried creating an aliases.json file on all of the systems, in the location suggested by, and with the same data shown by zookeeper cli "list": /aliases.json (0) DATA: {"collection":{"alias":"collection2,collection1"}} /collections (2) /collections/collection1 (2) .... The new collection didn't work until I issued zkcli upconfig & linkconfig commands that are issued when the zookeeper container starts, so perhaps I just need some additional zkcli incantations? Thanks In Advance! Phil Budne
