You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
VERISON
OrangoDB 3.10.1
The server is runing well for a long time until it got an error recentenly.
And we also found the relevant issue #16127
We set enforce-block-cache-size-limit = false in the starup.cfg,but it takes no effect.
We can't insert any record to any table even though we retart the OrangoDB server.
Please help to check this problem,thanks ~
The text was updated successfully, but these errors were encountered:
The error happens when there is no more capacity in the RocksDB block cache, and no other data in the block cache shard can be freed.
Can you try setting the startup option --rocksdb.enforce-block-cache-size-limit to false? That should help avoid this particular error.
Btw, version 3.10.1 is more than a year old, and 3.10.2 changed the value of the startup option to false. So even better than changing the value of the startup option and stay on 3.10.1 would be to upgrade to the newest version of 3.10, or even to 3.11.
We modify the arangod.conf,add line as
After this, we restart the server, the dbserver will still throw the error
It seems the particular error is not resolved.
Are you sure that the config file is being used, i.e. that the right config file was modified?
Because the option is supposed to work just fine, and if it doesn't, it is likely that it has been put into a config file that is not being used.
OK,this time, we set the enforce-block-cache-size-limit to false and we also drop the table that cause the error, and restart again, the error disappeared. Thanks~
VERISON
OrangoDB 3.10.1
The server is runing well for a long time until it got an error recentenly.
And we also found the relevant issue #16127
We set enforce-block-cache-size-limit = false in the starup.cfg,but it takes no effect.
We can't insert any record to any table even though we retart the OrangoDB server.
Please help to check this problem,thanks ~
The text was updated successfully, but these errors were encountered: