[
https://issues.apache.org/jira/browse/BEAM-2654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17131893#comment-17131893
]
Beam JIRA Bot commented on BEAM-2654:
-------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> io-it-suite profile: support ability to use other runners
> ---------------------------------------------------------
>
> Key: BEAM-2654
> URL: https://issues.apache.org/jira/browse/BEAM-2654
> Project: Beam
> Issue Type: Improvement
> Components: testing
> Reporter: Stephen Sisk
> Priority: P2
> Labels: stale-P2
>
> Currently, we do not have the ability to run integration tests on clusters of
> > 1 node using any runners other than dataflow. So we currently do not
> support the ability to invoke them in io-it-suite.
> Once we can run the integration tests on clusters of > 1 node, we'll want to
> be able to run the IO ITs on them. That involves:
> 1. In the io-it-suite profiles, we should have a runner flag or something
> like it to allow choosing a runner
> 2. Add support for them in dpb_service in PerfKit Benchmarker - flesh out
> dpb_service and beam_integration_benchmark for the newly supported runners.
> While we are building this, we should improve the mechanism by which we
> invoke the direct runner in io-it-suite. Currently, we use forceDirectRunner,
> which is a maven property that overrides the runner options/profiles to be
> added to the mvn invocation of io-it. We'll need to talk to the pkb team
> about how we should better support this since we'll need to make a
> modification on their side.
> cc [~iemejia] [~jasonkuster]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
