1. 04 4月, 2018 1 次提交
  2. 29 3月, 2018 1 次提交
    • K
      SystemLog: execute prepareTable() on each flush · b7429087
      Kirill Shvakov 提交于
      Merge remote-tracking branch 'upstream/master' into system-log-prepare-table-on-each-flush
      
      #2131 deleted excessive logging
      
      Revert "#2131 deleted excessive logging"
      
      This reverts commit d78a46d9.
      
      Revert "SystemLog: execute prepareTable()  on each flush"
      
      This reverts commit 7f60bb0a.
      
      SystemLog: execute prepareTable() on each flush
      b7429087
  3. 26 3月, 2018 1 次提交
  4. 24 3月, 2018 1 次提交
  5. 14 3月, 2018 3 次提交
  6. 13 3月, 2018 2 次提交
  7. 11 3月, 2018 2 次提交
  8. 10 3月, 2018 1 次提交
  9. 08 3月, 2018 2 次提交
  10. 02 3月, 2018 2 次提交
  11. 01 3月, 2018 2 次提交
  12. 25 2月, 2018 1 次提交
  13. 23 2月, 2018 1 次提交
  14. 22 2月, 2018 1 次提交
  15. 14 2月, 2018 3 次提交
  16. 01 2月, 2018 1 次提交
  17. 16 1月, 2018 1 次提交
  18. 15 1月, 2018 1 次提交
  19. 12 1月, 2018 2 次提交
  20. 23 12月, 2017 1 次提交
  21. 02 12月, 2017 1 次提交
  22. 30 11月, 2017 1 次提交
  23. 29 11月, 2017 1 次提交
  24. 28 11月, 2017 2 次提交
  25. 19 11月, 2017 1 次提交
  26. 18 11月, 2017 2 次提交
  27. 17 11月, 2017 1 次提交
    • S
      Basic idea is : · 64619c61
      Silviu Caragea 提交于
      - We add BackgroundSchedulePool which can execute a function at a specific point in time. Basically all tasks are added in a queue and precessed by worker threads.
      - The most important difference between this and BackgroundProcessingPool is that we have the guarantee that the same function is not executed from many workers in the same time
      - Each of the following classes instead starting a thread will register a task in BackgroundSchedulePool and when they need to run will call schedule or scheduleAfter(duration) functions
      
      This commit is moving all threads created by ReplicatedMergeTree to BackgroundSchedulePool tasks
      
      NOTE: I did a minimum number of changes to be much simple to review the code
      64619c61
  28. 16 11月, 2017 1 次提交