GitHub user greghogan opened a pull request:
https://github.com/apache/flink/pull/3249
[FLINK-3163] [scripts] Configure Flink for NUMA systems
Start a TaskManager on each NUMA node on each worker when the new
configuration option 'taskmanager.compute.numa' is enabled.
This does not affect the runtime process for the JobManager (or future
ResourceManager) as the startup scripts do not provide a simple means of
disambiguating masters and slaves. I expect most large clusters to run these
master processes on separate machines, and for small clusters the JobManager
can run alongside a TaskManager.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/greghogan/flink
3163_configure_flink_for_numa_systems
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/3249.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3249
----
commit 57767e67dc7306d18df07d5224c81a8d359df620
Author: Greg Hogan <c...@greghogan.com>
Date: 2017-02-01T17:13:49Z
[FLINK-3163] [scripts] Configure Flink for NUMA systems
Start a TaskManager on each NUMA node on each worker when the new
configuration option 'taskmanager.compute.numa' is enabled.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
