flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-7788) Allow port range for queryable state client proxy.
Date Thu, 12 Oct 2017 09:33:00 GMT

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

ASF GitHub Bot commented on FLINK-7788:
---------------------------------------

Github user aljoscha commented on a diff in the pull request:

    https://github.com/apache/flink/pull/4814#discussion_r144234905
  
    --- Diff: flink-core/src/main/java/org/apache/flink/configuration/QueryableStateOptions.java
---
    @@ -37,10 +37,27 @@
     			key("query.server.enable")
     			.defaultValue(true);
     
    -	/** Port to bind KvState server to (0 => pick random available port). */
    -	public static final ConfigOption<Integer> SERVER_PORT =
    +	/**
    +	 * The config parameter defining the server port range of the queryable state proxy.
    +	 *
    +	 * <p>A proxy runs on each Task Manager, so many proxies may run on the same
    +	 * machine.
    +	 *
    +	 * <p>Given this, and to avoid port clashes, the user can specify a port range
and
    +	 * the proxy is going to bind to the first free port in that range.
    +	 *
    +	 * <p>The specified range can be:
    +	 * <ol>
    +	 *     <li>a port: "9123",</li>
    --- End diff --
    
    I think the strange Javadoc convention (which is based on very old HTML) is to not have
closing `li` tags


> Allow port range for queryable state client proxy.
> --------------------------------------------------
>
>                 Key: FLINK-7788
>                 URL: https://issues.apache.org/jira/browse/FLINK-7788
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Queryable State
>    Affects Versions: 1.4.0
>            Reporter: Kostas Kloudas
>            Assignee: Kostas Kloudas
>             Fix For: 1.4.0
>
>
> Currently the newly introduced queryable state client proxy can only take one port as
a parameter to bind to. In case of multiple proxies running on one machine, this can result
in port clashes and inability to start the corresponding proxies. 
> This issue proposes to allow the specification of a port range, so that if some ports
in the range are occupied, the proxy can still pick from the remaining free ones.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message