Github user neykov commented on the issue:
https://github.com/apache/brooklyn-server/pull/565
To add some more context (without having looked at the changes) - before
adding ImmediateSupplier tasks with a short timeout (the way we implemented
"immediate") would get cancelled even before the thread had the chance to get
scheduled. So it's not all about whether the thread itself blocks for more than
what we are ready to wait for.
I think it's fine for ImmediateSupplier to take longer than ~200ms. That's
just a random limit we chose. It's easy to get over it on systems under load
when threads are involved - it was easily reproducible with just the clocker
blueprints. What matters is it knows it will finish in a sensible amount of
time and is not blocked indefinitely by tasks it doesn't have control over.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
