| 2019-07-30 20:08:37 |
Bjoern |
description |
Based on a production issue with a Liberty swift version (i know it's EOL) I noticed that the container_stats view contained invalid data, as
sqlite> select * from container_stat;
AUTH_2943f48102304a43a5bcf7eefbd22b01|mailstore-rs-119-1-104|1478133529.15135|147:133539&16340|0|1478133529.16340|0|15034|2207569538|cb43cd4935e5d079e0c0f00806bd0c67|f729fbd8-b79f-44c9-869d-d1c3da0cf01e||1478133529.16340||-1|-1|319046|0|15034|2207569538
the put timestamp contained 147:133539&16340 which should have been 1478133529.16340.
I suspect the issue was caused by 2 bits flipped, but the machine is running ECC memory and did not endure filesystem (XFS) issues or crashes so it remains a mystery where the corruption is happening.
Is there a reason why the put_timestamp was defined as text inside the source of the view (container_info table) rather than floating point or datetime, so we would hopefully recognize these issues during put requests? |
Based on a production issue with a Liberty swift version (i know it's EOL) I noticed that the container_stats view contained invalid data, as
sqlite> select * from container_stat;
AUTH_2943f48102304a43a5bcf7eefbd22b01|mailstore-rs-119-1-104|1478133529.15135|147:133539&16340|0|1478133529.16340|0|15034|2207569538|cb43cd4935e5d079e0c0f00806bd0c67|f729fbd8-b79f-44c9-869d-d1c3da0cf01e||1478133529.16340||-1|-1|319046|0|15034|2207569538
the put timestamp contained 147:133539&16340 which should have been 1478133529.16340.
I suspect the issue was caused by 2 bits flipped, but the machine is running ECC memory and did not endure filesystem (XFS) issues or crashes so it remains a mystery where the corruption is happening.
Is there a reason why the put_timestamp was defined as text inside the source of the view (container_info table) rather than floating point or datetime, so we would hopefully recognize these issues during put requests?
The corruption generates a 500 when querying the container service for the impacted database and I manually fixed the sqlite database to allow container listings to succeed now |
|
