Inconsistent Bucket Inventory and Actual Bucket Capacity

Problem Information

Problem Symptom

After objects are uploaded, the queried bucket inventory is inconsistent with the actual size of the uploaded objects.

Problem Diagnosis

1. Check the time interval between the upload and querying. If the time interval is less than 12.5 minutes, it is within the inventory statistics specifications and no further action is required.

2. Check whether the bucketusage process exists on a node.

3. Check whether the read and list performance is slow at the index layer.

Causes

1. If the bucket inventory is queried within 12.5 minutes after the objects are upload, it is normal that the inventory is inconsistent with the actual size of the uploaded objects. In this case, wait for a while and query again.

2. If the inventory update progress is far behind the current time, the inventory is presented as inaccurate and the quota is presented as unreliable. The possible cause is that the bucketusage process is suspended or the scanning speed is slow.

3. The possible cause of slow scanning speed is that a large number of objects are being uploaded and the amount of data to be scanned is large, or other processes are contending with the bucketusage process for resources.

Solution

1. If the update progress is not far behind the current time, wait until the gap increases and then solve the problem.

2. If the update progress is far behind the current time, restart the bucketusage process or reduce the service load on the client.

3. Contact technical support engineers.

Check After Recovery

The obtained bucket inventory is consistent with the actual size of uploaded objects. The inventory update progress is behind the current logical clock within 5 logical clocks.

Suggestion and Summary

Analyze the logs stored in the /var/log/obs/bucketusage/run directory to determine the latency of listing inventory data, facilitating problem location.

Applicable Versions

All