j

    jeev

    7 months ago
    Is there a default task timeout? Does it happen to be 48 hours by some chance? Is it configurable?
    @Greg Gydush
    Ketan (kumare3)

    Ketan (kumare3)

    7 months ago
    yes there is
    it is 48 hours, you need to change the config
    i think we should change the default to unlimited, cc @Kenny Workman
    @jeev you need to set this -
    core.yaml: |
        propeller:
          downstream-eval-duration: 30s
          enable-admin-launcher: true
          gc-interval: 12h
          node-config:
            default-deadlines:
              node-execution-deadline: 240h0m0s
              node-active-deadline: 240h0m0s
              workflow-active-deadline: 240h0m0s
    and can you file an issue for unlimited as the default?
    j

    jeev

    7 months ago
    awesome thanks @Ketan (kumare3)
    @Greg Gydush: fyi!
    also @Jay Ganbat
    Ketan (kumare3)

    Ketan (kumare3)

    7 months ago
    are you filing an issue?
    j

    jeev

    7 months ago
    we will
    k

    Kenny Workman

    7 months ago
    from my perspective / latch’s use case, default of unlimited is definitely expected so the timeout was unexpected
    so +1