[
https://issues.apache.org/jira/browse/FLINK-6095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhijiang updated FLINK-6095:
----------------------------
Description:
Currently all the parameters in {{SlotPool}} are hard coded including
{{DEFAULT_SLOT_REQUEST_TIMEOUT}}, {{DEFAULT_RM_ALLOCATION_TIMEOUT}},
{{DEFAULT_RM_REQUEST_TIMEOUT}}. Although there is another construction in
{{SlotPool}} to pass the values for tests, it is better and more flexible to
make them configurable for users in production.
It is part of work for Flip-6.
was:
Currently all the parameters in {{SlotPool}] are hard coded including
{{DEFAULT_SLOT_REQUEST_TIMEOUT}}, {{DEFAULT_RM_ALLOCATION_TIMEOUT}},
{{DEFAULT_RM_REQUEST_TIMEOUT}}. Although there is another construction in
{{SlotPool}} to pass the values for tests, it is better and more flexible to
make them configurable for users in production.
It is part of work for Flip-6.
> Introduce the SlotPoolOptions to config parameters for SlotPool
> ---------------------------------------------------------------
>
> Key: FLINK-6095
> URL: https://issues.apache.org/jira/browse/FLINK-6095
> Project: Flink
> Issue Type: Improvement
> Components: Distributed Coordination
> Reporter: zhijiang
> Assignee: zhijiang
> Priority: Minor
>
> Currently all the parameters in {{SlotPool}} are hard coded including
> {{DEFAULT_SLOT_REQUEST_TIMEOUT}}, {{DEFAULT_RM_ALLOCATION_TIMEOUT}},
> {{DEFAULT_RM_REQUEST_TIMEOUT}}. Although there is another construction in
> {{SlotPool}} to pass the values for tests, it is better and more flexible to
> make them configurable for users in production.
> It is part of work for Flip-6.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
