You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Stephan Erb (JIRA)" <ji...@apache.org> on 2018/01/31 11:31:00 UTC

[jira] [Commented] (AURORA-1233) primary_port warning does not appear to respect portmap

    [ https://issues.apache.org/jira/browse/AURORA-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16346644#comment-16346644 ] 

Stephan Erb commented on AURORA-1233:
-------------------------------------

Patch https://reviews.apache.org/r/65434/

> primary_port warning does not appear to respect portmap
> -------------------------------------------------------
>
>                 Key: AURORA-1233
>                 URL: https://issues.apache.org/jira/browse/AURORA-1233
>             Project: Aurora
>          Issue Type: Bug
>          Components: Client
>            Reporter: Kevin Sweeney
>            Priority: Minor
>
> From an internal bug report:
> {noformat}
> *Announcer specified primary port as 'thrift' but no processes have bound that port.
> If you would like to utilize this port, you should listen on {{thermos.ports\[thrift]}}
> from some Process bound to your task.*
> However, we *are* using that port in our Process.
> '-fetcher_port={{thermos.ports\[thrift]}}',
> It seems that when the primary port is statically linked, it causes this warning.
> announce = Announcer(primary_port = 'thrift', portmap = {'thrift': 10001, 'http': 8080, 'aurora': 'http', 'health': 'http'}
> If I don't statically link it, then it runs as normal.
> FYI: Everything works as expected. The only issue is that warning/error is displayed in error.
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)