On 9/20/23 06:59, Matias Laino wrote:
Hello everyone, we recently upgraded our hard drives on our EC2 instances of our solrcloud, because we were running out of space, after doing that, all of our nodes stopped showing disk information, number of records per collection and solr is in general working really bad, to the point that I’m considering reinstalling new servers.
That's a problem with hardware and/or the operating system. Solr does not get involved at that level. If you're having trouble with that, you may need to get help from Amazon. They are a lot less likely to give you info that screws up your EC2 instance than a mailing list like this one.
Based on what you have said, my first course of action would be to reboot the instance and see if that helps at all.
I have increased the size of the storage on my EC2 instance. This action produced no notable difference in the running Linux install other than new data in the kernel log showing that the size of a storage volume changed.
After making the change on the AWS UI, I was able to increase the size of the partition containing my root filesystem (I think I used parted for that, but don't remember for sure), and then use filesystem tools (ext4 in my case) to extend the filesystem. All without stopping software or rebooting the system.
I know that this filesystem extension capability exists for ext4 and xfs. I think zfs and btrfs can also be extended while online, but I have not verified this. I do not know much about any other filesystem types on Linux.
If your instance uses LVM, then you have to extend the PV, VG, and LV after extending the partition and before doing the filesystem. My EC2 instance is not using LVM.
Thanks, Shawn
