Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Unresolved
-
6.1.1
-
None
-
None
-
centos ec2 using s3 for storage
Description
Client has s3 storage on a 3 node cluster. Cluster has been up for 280 days.
All em_saves are from 2021 so are not being saved to disk. This looks to be a miss in logic and introduces risk having no real save_em files to fall back on.
[] root@demo-mcs1: centos # aws s3 ls s3://mcs-demo-bucketXX | grep _em
|
2021-09-29 19:13:19 4199180 18f2fdd1-940e-489f-ba14-2e88b0d9588a_0_4199180_data1~systemFiles~dbrm~BRM_savesB_em
|
2021-09-23 11:17:13 4748 4511dbf0-08de-4f2e-9594-0fbb4e4ebc72_0_4748_data1~systemFiles~dbrm~BRM_savesA_em
|
2021-09-23 11:17:12 4652 484f8352-92ec-4be7-a6ea-80e6db4ba0c3_0_4652_data1~systemFiles~dbrm~BRM_savesB_em
|
2021-11-22 13:35:58 5242880 5c4c58d2-2ce7-400e-8f92-ea73f56d11db_0_5242880_data1~systemFiles~dbrm~BRM_saves_em
|
2021-11-22 13:35:58 8940 6a7470d6-eab6-4d7a-b572-f20a8a9a6d62_5242880_8940_data1~systemFiles~dbrm~BRM_saves_em
|
2021-09-24 11:41:31 4098188 6b3fb895-530a-4676-9709-e1ac001f383e_0_4098188_data1~systemFiles~dbrm~BRM_saves_em
|
2021-10-06 14:07:24 4397516 76b68b37-90b4-4436-a208-248bdf0b1dad_0_4397516_data1~systemFiles~dbrm~BRM_savesA_em
|
2021-09-23 11:17:12 4748 7ece8e55-202f-46a6-969a-98464c9b5bdc_0_4748_data1~systemFiles~dbrm~BRM_savesA_em
|
2021-09-23 22:04:31 4108844 87713192-f985-496c-ba49-bfa2c3df6f22_0_4108844_data1~systemFiles~dbrm~BRM_saves_em
|
2021-09-23 11:17:12 4652 f2f90b6f-2468-4ca7-b0e9-d0c3434c0c9b_0_4652_data1~systemFiles~dbrm~BRM_savesB_em
|
[] root@demo-mcs1: centos # cat /var/lib/columnstore/storagemanager/metadata/data1/systemFiles/dbrm/BRM_saves_em.meta
|
{
|
"version": "1",
|
"revision": "1",
|
"objects":
|
[
|
{
|
"offset": "0",
|
"length": "5242880",
|
"key": "5c4c58d2-2ce7-400e-8f92-ea73f56d11db_0_5242880_data1~systemFiles~dbrm~BRM_saves_em"
|
},
|
{
|
"offset": "5242880",
|
"length": "8940",
|
"key": "6a7470d6-eab6-4d7a-b572-f20a8a9a6d62_5242880_8940_data1~systemFiles~dbrm~BRM_saves_em"
|
}
|
]
|
|