Add func tests run with s3 and fix several bugs#34215
Conversation
|
If it will work, need to add a lot of comments. |
This reverts commit 3c80e0b.
|
Reverted #34219 in this PR. |
|
Need to implement proper fix. |
|
Strategy picker fundamentally bad idea. Better to implement exclusive locks for merges and mutations. |
|
One known bug left: lock part during fetch with ephemeral lock. |
|
Also need fix for sparse with wide parts -- separate PR. |
|
I hope I've fixed everything. So one more run with all sanitizers and run with a single check. |
ac778a6 to
b75d551
Compare
| } | ||
| } | ||
|
|
||
| /// Load metadata by path or create empty if `create` flag is set. |
There was a problem hiding this comment.
There is no create flag anymore
There was a problem hiding this comment.
Yes, what do you thing about using local fs hardlink count? Why do you think it is bad idea?
There was a problem hiding this comment.
I don't fully understand the purpose of userland hardlink tracking. However, if we somehow need to do it properly, we will have to synchronize every file operation which can change the hardlink property. If the mutex is per-disk, it will be too heavy, since some common mutation like DROP COLUMN can generate tons of hardlinks. I don't know how good flock is, but it smells bad.
|
No, one more race during fetch... |
|
I'll try to add comments. |
|
Tests should be Ok, but we have to fix non-user-visible in the next PRs:
|
Changelog category (leave one):