[
https://issues.apache.org/jira/browse/AURORA-1212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14384601#comment-14384601
]
Bill Farner commented on AURORA-1212:
-------------------------------------
Apparently this JIRA is not configured to post e-mail replies, copying my reply:
My apologies for the delay, I have been out of town this week and otherwise
occupied by quarter boundary work.
I would like to better understand your use case and the technical barriers
before we proceed. I will email you to arrange that discussion. In the
meantime, you might consider running a custom build with your patch. Another
option is announcing in the application layer. This would give you more
control over the contents of the znodes without leaning on Aurora to allow use
of static ports.
Ultimately my hesitance is about providing good guidance to users, and I wish
to advise against use of static ports as it will not scale. Additionally, as
Aurora and mesos continue to mature, I want to make sure we do not backpedal on
use cases we previously condoned through accepted patches.
I hope to get you unblocked soon in some way. I trust you understand that It's
important to me that I fully understand use cases so that I can defend them in
the future as the system evolves.
> Allow non-dedicated jobs to have static ports
> ---------------------------------------------
>
> Key: AURORA-1212
> URL: https://issues.apache.org/jira/browse/AURORA-1212
> Project: Aurora
> Issue Type: Story
> Reporter: Brian Brazil
>
> In my environment I'd like to have static ports for some jobs to integrate
> with some services that don't do service discovery, but I don't want to have
> to partition my users up onto dedicated machines just for this.
> Currently the aurora client rejects such a configuration, it should be
> allowed.
> https://github.com/apache/incubator-aurora/commit/bcabfce60d568d5d98c72109ee4493bce773a426
> was where this restriction was added.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
