- 12 3月, 2021 1 次提交
-
-
由 Pavel Kruglov 提交于
-
- 05 3月, 2021 12 次提交
-
-
由 gyuton 提交于
Co-authored-by: Nolgarev <56617294+olgarev@users.noreply.github.com> Co-authored-by: NGeorge <gyuton@yandex-team.ru>
-
由 Kruglov Pavel 提交于
Update in.md
-
由 Nikolai Kochetov 提交于
Try fix perftests.
-
由 alesapin 提交于
Use path as default prefix for coordination logs
-
由 alexey-milovidov 提交于
Tiny fix
-
由 Alexander Kuzmenkov 提交于
DOCSUP-4707: Edit and translate to Russian
-
由 alexey-milovidov 提交于
-
由 alexey-milovidov 提交于
-
由 Nikita Mikhaylov 提交于
Fix ParsingException::displayText()
-
由 tavplubix 提交于
Try fix MaterializeMySQL integration test
-
由 Dmitriy 提交于
Добавил ссылки на продукты, убрал кавычки со стандарта.
-
由 Amos Bird 提交于
-
- 04 3月, 2021 27 次提交
-
-
由 Kseniia Sumarokova 提交于
Case-insensitive compression methods for table functions
-
由 alesapin 提交于
-
由 Ivan 提交于
Add ability to throttle INSERT into Distributed
-
由 Nikolai Kochetov 提交于
-
由 DIAOZHAFENG 提交于
-
由 DIAOZHAFENG 提交于
update untranslated line
-
由 Nikolai Kochetov 提交于
Fix SIGSEGV for distributed queries on failures
-
由 alesapin 提交于
-
由 olgarev 提交于
Co-authored-by: Nana-uvarova <ana-uvarova@yandex-team.ru> Co-authored-by: NAnaUvarova <64017504+AnaUvarova@users.noreply.github.com> Co-authored-by: Nvdimir <vdimir@yandex-team.ru> Co-authored-by: NOlga Revyakina <revolg@yandex-team.ru> Co-authored-by: NAnna <42538400+adevyatova@users.noreply.github.com>
-
由 Azat Khuzhin 提交于
Since after pull(), cancel() will be called, and this will lead to SIGSEGV, since there is no exception, but has_exception was not reseted in pull()
-
由 Azat Khuzhin 提交于
Before it was silently try-catched for messages with additional {}, and it is very easy to trigger, i.e.: SELECT toDateTime(format('{}-{}-01 00:00:00', '2021', '1')) Will print: Code: 41. DB::Exception: Received from localhost:9000. DB::Exception: Cannot parse datetime 2021-1-01 00:00:00{}: Cannot parse DateTime from String: while executing 'FUNCTION toDateTime(format('{}-{}-01 00:00:00', '2021', '1') :: 3) -> toDateTime(format('{}-{}-01 00:00:00', '2021', '1')) DateTime : 2'.
-
由 Azat Khuzhin 提交于
-
由 Azat Khuzhin 提交于
Before it was checked for each block.
-
由 Azat Khuzhin 提交于
-
由 Azat Khuzhin 提交于
-
由 Azat Khuzhin 提交于
Add two new settings for the Distributed engine: - bytes_to_delay_insert - max_delay_to_insert If at the beginning of INSERT there will be too much pending data, more then bytes_to_delay_insert, then the INSERT will wait until it will be shrinked, and not more then max_delay_to_insert seconds. If after this there will be still too much pending, it will throw an exception. Also new profile events were added (by analogy to the MergeTree): - DistributedDelayedInserts (although you can use system.errors instead of this, but still) - DistributedRejectedInserts - DistributedDelayedInsertsMilliseconds
-
由 Azat Khuzhin 提交于
Since there is local value, that is not atomic, anyway we already have lock for metrics, so it is fine.
-
由 Azat Khuzhin 提交于
-
由 Azat Khuzhin 提交于
-
由 Azat Khuzhin 提交于
-
由 Azat Khuzhin 提交于
It is more natural, since we do not need lazy locking.
-
由 Azat Khuzhin 提交于
Previous patch fixes the inaccuracy, but it's done using iterating over directory on each request (to system.distribution_queue or to check bytes_to_throw_insert), and like previous patch alredy stated, it may have pretty huge overhead (especially when you have lots of distributed files pending). This patch remove that recalculation (but it will still be done, and if there is different, there will be a log message), and replace it with proper account at INSERT time (and after file has been sent, or marked as broken).
-
由 Azat Khuzhin 提交于
So now system.distribution_queue will show accurate statistics, so tests does not requires sleep anymore. But note that with too much distributed pending this will iterate over all directories.
-
由 Azat Khuzhin 提交于
Right now with distributed_directory_monitor_batch_inserts=1 and insert_distributed_sync=0 INSERT into Distributed table will store blocks that should be sent to remote (and in case of prefer_localhost_replica=0 to the localhost too) on the local filesystem, and sent it in background. However there is no limit for this storage, and if the remote is unavailable (or some other error), these pending blocks may take significant space, and this is not always desired behaviour. Add new Distributed setting - bytes_to_throw_insert, that will set the limit for how much pending bytes is allowed, if the limit will be reached an exception will be throw. By default was set to 0, to avoid surprises.
-
由 Azat Khuzhin 提交于
-
由 Azat Khuzhin 提交于
-
由 Azat Khuzhin 提交于
-