-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
backend abm: Unlink of "/mnt/ssd1/arakoon/sas-back-abm/db/touch-20625" failed with ENOENT #2315
Comments
If this is a 3 (or more) node cluster, and it's just this node that's acting up, and it has been for a while now, it means that the other nodes in the cluster can continue without this one and this one is severely lagging anyway. If there's a large number of tlogs, you might want to run a collapse on the other nodes first (this is probably done once a day by the framework) |
This is a 3-node cluster. I checked the other nodes. The tlogs on this node are really lagging behind a lot. Here's a look please.
BTW, what do you mean |
this is an abm, so lots of tlogs but a small database. It's better to do this:
It will, for the other nodes, copy the database to the head and keep 10 tlogs. This will make catchup fast. |
OK. I emptied this abm's db (except 'albamgr_plugin.cmxs') and tlogs but I didn't collapse on the other nodes. I can see this node is catching up from 001.tlog/tlx and it looks going to reach 37613.tlx at least. It may take many days. Shall i stop the abm service and re-empty its db and tlogs directories? |
Did you run |
No, I didn't run |
I stopped On node1, I ran But on node2, I got the following error:
All these 3 nodes are master nodes. |
Then, restart the wiped arakoon on the 3rd node. |
OK, |
Hello,
ovs-arakoon-sas-back-abm.service
keeps on activating but it cannot start up. It has been like for a few weeks. Just wondering whats' going on:Best regards,
Yongsheng
The text was updated successfully, but these errors were encountered: