Closed qkrorlqr closed 4 days ago
TEST NAME ELAPSED STATUS LOG cloud/filestore/tests/fs_posix_compliance/qemu-kikimr-nemesis-test/[0/7] chunk chunk 0.000s FAIL DIR | LOG | STDERR | RECIPE_STDERR | RECIPE_STDOUT cloud/filestore/tests/fs_posix_compliance/qemu-kikimr-nemesis-test/test.py.test_posix_compliance[flock] 9m 24.309s FAIL(TIMEOUT) DIR | LOG
флап, чиню тут https://github.com/ydb-platform/nbs/pull/1520
DupCache entry commit was simply forgotten for the multi-tablet mode in my previous PRs. And as for TabletProxy - we send various requests to IndexTablets via TabletProxy and there is some weird logic in IndexTablet which sends EvPoisonPill in response to some previously sent CreateSessionRequests - this logic controls the lifecycle of the CreateSessionActor and is quite fragile so I'm not planning to change it right now. But this logic might kill TabletProxy in some cases which renders the filestore-server instance almost unusable. VolumeProxy in NBS is already immortal - making TabletProxy immortal in a similar fashion. As for the inactive pipe tracking logic - it's not really needed and it messes with the leader->follower session creation logic (followers destroy sessions after pipe destruction which breaks some scenarios). Deleting that unneeded logic is the most straightforward solution.
1350