incubator-s4-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthieu Morel (JIRA)" <>
Subject [jira] [Commented] (S4-71) s4 deploy mismanages s4r URI
Date Mon, 09 Jul 2012 10:55:35 GMT


Matthieu Morel commented on S4-71:

# I removed the appsDir setting so that files are retrieved and copied in local temporary
locations for each S4 node 
# I added an option -generatedS4R that specifies where to copy the generated S4R

In addition, I :
# refactored the code so that only 1 app can be deployed. This means that there is a single
Zookeeper node in /s4/clusterX/app that contains the information about the application for
this cluster. Using a Zookeeper directory does not make sense as we want to only deploy a
single app per S4 subcluster.
# improved the producer/consumer regression test, by deploying a producer app and a consumer
app in separate subclusters, and checking effective communication between them
# updated cluster resolution from the comm layer is now performed upon S4 node initialization,
so that it does not need to be triggered by sending a message, thereby avoiding {{ERROR org.apache.s4.comm.tcp.TCPEmitter
- No ClusterNode exists for partitionId 0}} messages

Patch is available in branch S4-71 (;a=shortlog;h=refs/heads/S4-71

> s4 deploy mismanages s4r URI
> ----------------------------
>                 Key: S4-71
>                 URL:
>             Project: Apache S4
>          Issue Type: Bug
>    Affects Versions: 0.5
>            Reporter: Matthieu Morel
>            Assignee: Matthieu Morel
>             Fix For: 0.5
> # -s4r parameter is considered but the URI in the "app" znode refers to a local copy
of the specified file
> # without -s4r parameter, when combining application building and uploading (mostly for
testing purposes), we need a parameter that indicates where to copy the generated s4r (therefore
which URI will be referred to in the "app" znode)

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message