-
Notifications
You must be signed in to change notification settings - Fork 567
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
viewer healthcheck pathmerge stable 24 3 11 hotfix #11042
Closed
StekPerepolnen
wants to merge
250
commits into
ydb-platform:main
from
StekPerepolnen:viewer-healthcheck-pathmerge-stable-24-3-11-hotfix
Closed
viewer healthcheck pathmerge stable 24 3 11 hotfix #11042
StekPerepolnen
wants to merge
250
commits into
ydb-platform:main
from
StekPerepolnen:viewer-healthcheck-pathmerge-stable-24-3-11-hotfix
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: Tony-Romanov <[email protected]>
… emitting of resolved timestamps (ydb-platform#6616)
…form#6625) (ydb-platform#6694) Co-authored-by: mregrock <[email protected]> Co-authored-by: Egor Kulin <[email protected]>
…lt (ydb-platform#6847) merged 83a86c2 from main Preserialize table's split boundaries the same way table partitions are. The size of both depend on the same variable: number of shards in the table, but TablePartitions was preserialized (and cached) while Table.SplitBoundaries wasn't. Preserializing all potentially huge parts of DescribeSchemeResult message before it gets to the interconnect saves interconnect actors additional serialization costs. And when partitioning of the huge tables goes through the period of a rapid change that additional serialization causes interconnect to overload. Single shortcoming though: preserialized SplitBoundary is not used (cannot be used) when boundaries of the index tables are requested through describe request on table index. KIKIMR-21686
…b-platform#6760) (ydb-platform#6849) merged ebee36a from main Add commit redo size check for successfully ignited operations as a precaution measure to avoid infinite loop of schemeshard hitting local tx commit redo size limit, restarting, attempting to propose persisted operation again, hitting commit redo size limit again, restarting and so on. This could happen with inherently massive operations such as copy-tables used as a starting step of database export/backup. Coping large number of tables with huge number of partitions can result in so large TTxOperationPropose local transaction that its size would hit the limit imposed by the tablet executor. Tablet violating that limit is considered broken and will be immediately stopped. See ydb/core/tablet_flat/flat_executor.cpp, NTabletFlatExecutor::TExecutor::ExecuteTransaction(). KIKIMR-21751
Co-authored-by: antonkovalenko <[email protected]>
Co-authored-by: kruall <[email protected]>
🔴 Unable to merge your PR into the base branch. Please rebase or merge it with the base branch. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
TEvProposeTransaction
andTEvLockStatus
(The race betweenTEvProposeTransaction
andTEvLockStatus
#8517) (The race betweenTEvProposeTransaction
andTEvLockStatus
(#8517) #8670)EnablePQConfigTransactionsAtSchemeshard
andEnableTopicServiceTx
(Default values for feature flagsEnablePQConfigTransactionsAtSchemeshard
andEnableTopicServiceTx
#8845)TEvTxCalcPredicate
message for the completed transaction (theTEvTxCalcPredicate
message for the completed transaction #8809) (theTEvTxCalcPredicate
message for the completed transaction (#8809) #9225)DescripeTopic
call with theIncludeStats
flag freezes (TheDescripeTopic
call with theIncludeStats
flag freezes #9392) (TheDescripeTopic
call with theIncludeStats
flag freezes (#9392) #9415)TEvProposePartitionConfig
message is sent only to the main partitions (TheTEvProposePartitionConfig
message is sent only to the main partitions #9599) (TheTEvProposePartitionConfig
message is sent only to the main partitions (#9599) #9632)WITH (security_invoker = true)
#9320 (Views: throw a human-readable error in case of a missing WITH (security_invoker = true) #9320 #9783)Changelog entry
...
Changelog category
Additional information
...