We should hold off until it is solved. How long will it take to fix this?
On Sun, May 14, 2017 at 10:13 PM, Navina Ramesh (Apache)
wrote:
> I just changed the status of this JIRA to "BLOCKER" -
> https://issues.apache.org/jira/browse/SAMZA-1128
>
> This causes a bug in standalone deployment wher
I just changed the status of this JIRA to "BLOCKER" -
https://issues.apache.org/jira/browse/SAMZA-1128
This causes a bug in standalone deployment where any failure in the barrier
protocol stops the scheduled executorservice. Unfortunately,
CoordinationUtils creates its own scheduled executorservic
I think we need to add SAMZA-1286 and
SAMZA-1279 to the release .
On Wed, May 10, 2017 at 7:51 PM, Jagadish Venkatraman
wrote:
> This is a call for a vote on a release of Apache Samza 0.13.0. Thanks to
> everyone who has contributed to this release. We are very glad to see some
> new contributor
