The issue:
Hello there, good day to you!
I’ve a self manage cluster with podman compose I was running studies in (mainly about performance and storage size of my current dataset) because we are planning a migration to yugabytedb from mongodb. And one of the times I restarted the server it returned this error when connecting:
Table with identifier 000000010000300080000000000004ec not found: OBJECT_NOT_FOUND
The server has an attached volume, and it’s the host is Fedora 41 with ext4 file system.
I’ve removed the volume and started the server again, which solved the issue, however If I were to run it in production, this cannot happen. Can you explain why it happen? If it’s a configuration issue? What are the steps to prevent it happening again? What can I do to restore the data If it were to happened?
In the real deployment we are going to use podman volume export to backup the data from the server. Would this be a problem? Is there a better way to back it up (please keep in mind, I need to run a backup every 6 hours)?
Configuration:
compose.yml:
version: "3"
volumes:
yugabyte-data:
driver: local
networks:
default: {}
services:
yugabyte:
image: docker.io/yugabytedb/yugabyte:latest
tty: true
container_name: yugabytedb
environment:
YSQL_USER: ${yugabyte_user}
YSQL_DB: fancyfone
YSQL_PASSWORD: ${yugabyte_password}
networks:
default:
aliases:
- yugabytedb
command: ./bin/yugabyted start --advertise_address=yugabytedb --cloud_location=aws.us-east-1.us-east-1a --fault_tolerance=zone --background=false --base_dir=/home/yugabyte/yb_data
ports:
- 7100:7100 # YB-Master
- 9100:9100 # YB-TServer
- 15433:15433 # YB-UI
- 5433:5433 # YSQL
- 9042:9042 # YCQL
volumes:
- yugabyte-data:/home/yugabyte/yb_data
I run this cluster on Hetzner, because of the size of the data, it’s not feasible to run multiple nodes right now, but we may look into adding extra nodes in the future, once it becomes feasible.
I found the