`REP 3` in four node env with two failures. No placement, but at least one copy available, which should be possible to fetch. #139

New issue

Open

opened 2025-12-28 18:07:10 +00:00 by sami · 1 comment

sami commented

2025-12-28 18:07:10 +00:00

Owner

Originally created by @fyrchik on GitHub (Oct 18, 2022).

sami added the

bug

labels

2025-12-28 18:07:10 +00:00

sami commented

2025-12-28 18:07:11 +00:00

Author

Owner

@roman-khimov commented on GitHub (Jan 27, 2023):

Can be solved with some specific "not enough nodes" error returned from SDK and then used by the node to fallback to dropping the number of replicas for reads. Reads should not be denied in this case of course.

Although given that the same code can be used by other clients reading objects, maybe implementing this logic in SDK is also an option. But it also starts with a case-specific error.

@roman-khimov commented on GitHub (Jan 27, 2023): Can be solved with some specific "not enough nodes" error returned from SDK and then used by the node to fallback to dropping the number of replicas for reads. Reads should not be denied in this case of course. Although given that the same code can be used by other clients reading objects, maybe implementing this logic in SDK is also an option. But it also starts with a case-specific error.