Stop controller from placing extents on readonly stores

uber-archive / cherami-server

Distributed, scalable, durable, and highly available message queue system. This project is deprecated and not maintained.

https://eng.uber.com/cherami/

MIT License

1.42k stars 102 forks source link

Stop controller from placing extents on readonly stores #325

Closed kirg closed 6 years ago

kirg commented 6 years ago

storehosts that are 'read-only' (due to low-space), would emit a (new) node-metric to controller
controller would stop placing extents on stores that are read-only

This change relies on a thrift change, tracked by this PR: https://github.com/uber/cherami-thrift/pull/29

coveralls commented 6 years ago

Coverage increased (+0.3%) to 66.943% when pulling 2f23934daccdd6d5b2f265b74b53d96e88a1f123 on storehost-readonly-notify into 65a1bb1404b63ce07025a2a3f6d34187fddce030 on master.

kirg commented 6 years ago

@thuningxu No, I couldn't find any unit tests that tests placement specifically.