Expose port offset in Sparkling Water

[exalate-issue-sync]

implemented in H2O in https://github.com/h2oai/h2o-3/pull/2678/files

[exalate-issue-sync]

Jakub Hava commented: In Sparkling Water, it is good approach to be able to separately configure options for client (can be for example edge node) and rest of the worker nodes.

However the implementation of _port_offset is broken in H2O in terms of when we specify different port offset to different H2O nodes. See [PUBDEV-5800]

This change will port the -port_offset to Sparkling Water, however it will be valid for the whole cluster at this moment

[DinukaH2O]

JIRA Issue Migration Info

Jira Issue: SW-965
Assignee: Jakub Hava
Reporter: Jakub Hava
State: Resolved
Fix Version: 2.1.35
Attachments: N/A
Development PRs: Available

Linked PRs from JIRA

#866

[hasithjp]

JIRA Issue Migration Info Cont'd

Jira Issue Created Date: 2018-07-29T23:47:56.659-0700