You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Chris Riccomini (JIRA)" <ji...@apache.org> on 2015/01/14 18:30:36 UTC

[jira] [Commented] (SAMZA-509) Supporting integration test execution on multiple machines

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

Chris Riccomini commented on SAMZA-509:
---------------------------------------

Linking to SAMZA-508 since we need to be able to execute on non-local machines before we can make the tests multi-node.

> Supporting integration test execution on multiple machines
> ----------------------------------------------------------
>
>                 Key: SAMZA-509
>                 URL: https://issues.apache.org/jira/browse/SAMZA-509
>             Project: Samza
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 0.9.0
>            Reporter: Chris Riccomini
>
> Samza's integration tests can't be executed on multiple machines right now. This is because all existing configs for Kafka, YARN, and ZK point to localhost. We should convert Kafka, YARN, and ZK to use templated configs (samza-test/src/main/python/templates) to generate proper configs for every machine in deployment host lists (located in samza-test/src/main/python/configs/*json). Once this is done, we can properly generate configs for every machine in the deployment machine list.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)