As they are unassigned, Elasticsearch does not know the size, so that is natural. Monitor the number of assigned/unassigned shards and see if this changes over time.
I don't see any changes, everything like before
"unassigned_shards" : 169,
No some data in logs
maybe I need to try to use
allocate_stale_primary
but I did not get how to use it properly
Christian, could you recommend something?
As you potentially have had a network partition and tried to resolve the issue during this you may have suffered data loss. If closing and reopening indices does not work it may be necessary to delete them and restore from a backup (I saw that you have the repository-s3 plugin installed).
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.