Hello Erik,
Thank you for clarifying the doubt. That was the exact concern I was having.
On Tue, Mar 29, 2016 at 9:05 PM, Erik Weathers
wrote:
> hi Pradeep,
>
> Yes, that would *definitely* be a problem. e.g., the Storm Framework
> could easily assign Storm Workers to use those unavailable p
hi Pradeep,
Yes, that would *definitely* be a problem. e.g., the Storm Framework could
easily assign Storm Workers to use those unavailable ports, and then they
would fail to come up since they wouldn't be able to bind to their assigned
port. I've answered a similar question before:
https://uni
Hi Klaus,
Thank you for the quick reply.
One quick question:
I have some of the ports like 8400,8500,8600 which are already in use by
consul agent running on each mesos slave. But they are also being announced
by each mesos slave. Will this cause any problem to tasks which maybe
assigned those p
Yes, all port resources must be ranges for now, e.g. 31000-35000.
There’s already JIRA (MESOS-4627: Improve Ranges parsing to handle single
values) on that, patches are pending on review :).
Da (Klaus), Ma (马达) | PMP® | Advisory Software Engineer Platform OpenSource
Technology, STG, IBM GCG +
4 matches
Mail list logo
