1. 11 1月, 2021 1 次提交
  2. 28 12月, 2020 1 次提交
  3. 25 12月, 2020 2 次提交
  4. 23 12月, 2020 1 次提交
  5. 24 11月, 2020 1 次提交
  6. 08 11月, 2020 3 次提交
  7. 05 11月, 2020 7 次提交
  8. 27 10月, 2020 1 次提交
  9. 22 10月, 2020 1 次提交
  10. 22 9月, 2020 1 次提交
  11. 28 8月, 2020 1 次提交
  12. 27 8月, 2020 3 次提交
  13. 25 8月, 2020 1 次提交
  14. 21 8月, 2020 1 次提交
  15. 07 8月, 2020 3 次提交
  16. 24 6月, 2020 1 次提交
  17. 23 6月, 2020 1 次提交
    • A
      [FLINK-18353] Make enabling of the JVM Direct Memory limit configurable for JM · dcd96025
      Andrey Zagrebin 提交于
      The JVM Direct Memory leak is unlikely in JM. Therefore, we could
      disable its limit by default. This way it could span into e.g. JVM
      Overhead w/o failure to improve the user experience as before FLIP-116.
      If user needs the limit, e.g. to investigate container OOMs, the limit can be enabled by
      setting the 'jobmanager.memory.enable-jvm-direct-memory-limit' option.
      
      This closes #12745.
      dcd96025
  18. 14 6月, 2020 1 次提交
    • X
      [FLINK-18226][runtime] Fix ActiveResourceManager request extra workers on... · 4f333e54
      Xintong Song 提交于
      [FLINK-18226][runtime] Fix ActiveResourceManager request extra workers on termination of existing workers.
      
      ActiveResourceManager decides whether and how many new wokers to request based on the following equation.
      
      	workersToRequest = workersRequiredBySlotManager - workersRequestedByResourceManagerNotRegistered
      
      where previsoutly 'workersRequestedByResourceManagerNotRegistered' was 'workersRequestedByResourceManagerNotAllocated'.
      
      This closes #12620.
      4f333e54
  19. 08 6月, 2020 1 次提交
  20. 04 6月, 2020 3 次提交
  21. 26 5月, 2020 2 次提交
  22. 17 5月, 2020 3 次提交