-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
store: Added test for consistency delay filter, defaulted to 0. #2159
Conversation
cc @khyatisoneji : We missed a unit test for that. Also moving to default consistency delay to 0. This is to not surprise users. In fact you only need this when you have eventually consistent object storage, am I right? (: |
471b170
to
eda3b2f
Compare
Signed-off-by: Bartlomiej Plotka <[email protected]>
eda3b2f
to
703773c
Compare
Should we have documentation on what appropriate values might be for various providers? For example with AWS S3's read-after-write consistency we have no problem with a consistency delay of 0 is my understanding. |
Yes. At least.. we did not notice anything wrong with S3. Eventual consistency can have really different tmp side effects. In theory we kind of DON'T hit the thing mentioned by S3 as the one that triggers eventual consistent behavior: a HEAD against the path that is later used. We only do that for meta.json: Line 297 in 55cb8ca
So it's fine I guess. But all of this is not well documented by S3. I think having some small consistency delay might be helpful just in case. Also, this is still crippled as we check block creation time, not the actual modification time of file. |
As these are tests nothing needs to be added to the Changelog, correct? Just rebase the release branch to include it?! |
Yup. We already have entry for it. |
yeah I'm saying writing down expected things and correcting them as we learn also helps the community and users :) |
Makes sense to me, this is not to surprise the users. OTOH there's no bad side effect if we will start serving data from remote object storage only after 30 minutes except that it might not be intuitive. All in all, let's opt for the principle of least surprise but some docs would indeed be nice 👍 |
…os-io#2159) Signed-off-by: Bartlomiej Plotka <[email protected]>
Signed-off-by: Bartlomiej Plotka [email protected]