About reconnect times?

Hi Guys, One of brokers in Kafka cluster is going down, the samza got the following exception: 2017-04-19 10:42:36.751 [SAMZA-BROKER-PROXY-BrokerProxy thread pointed at 172.19.105.20:9096 for client samza_consumer-canal_status_content_distinct-1] DefaultFetchSimpleConsumer [INFO]

[GitHub] samza pull request #130: SAMZA-1217: Fix broken build due to TestCheckstyle ...

Github user asfgit closed the pull request at: https://github.com/apache/samza/pull/130 --- 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

[GitHub] samza pull request #130: SAMZA-1217: Fix broken build due to TestCheckstyle ...

GitHub user shanthoosh opened a pull request: https://github.com/apache/samza/pull/130 SAMZA-1217: Fix broken build due to TestCheckstyle problem in trunk You can merge this pull request into a Git repository by running: $ git pull https://github.com/shanthoosh/samza master

[GitHub] samza pull request #128: SAMZA-1157: Serialization/deserialization throwable...

Github user asfgit closed the pull request at: https://github.com/apache/samza/pull/128 --- 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

[GitHub] samza pull request #129: SAMZA-1215, SAMZA-1216: remove ProcessKiller and ch...

Github user asfgit closed the pull request at: https://github.com/apache/samza/pull/129 --- 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

[GitHub] samza pull request #129: SAMZA-1215, SAMZA-1216: remove ProcessKiller and ch...

GitHub user nickpan47 opened a pull request: https://github.com/apache/samza/pull/129 SAMZA-1215, SAMZA-1216: remove ProcessKiller and change the ZooKeeper connection string in test … test to use 127.0.0.1 in connect string You can merge this pull request into a Git repository

[GitHub] samza pull request #128: SAMZA-1157: Serialization/deserialization throwable...

GitHub user nickpan47 opened a pull request: https://github.com/apache/samza/pull/128 SAMZA-1157: Serialization/deserialization throwables should not be suppressed …ppressed if user don't configure to drop those errors You can merge this pull request into a Git repository by

[GitHub] samza pull request #126: SAMZA-1182 : Disable flaky tests.

Github user asfgit closed the pull request at: https://github.com/apache/samza/pull/126 --- 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

[GitHub] samza pull request #127: SAMZA-1204: Visualize StreamGraph and ExecutionPlan

GitHub user xinyuiscool opened a pull request: https://github.com/apache/samza/pull/127 SAMZA-1204: Visualize StreamGraph and ExecutionPlan First look: https://xinyuiscool.github.io/visualizer/plan.html. This is based on the example graph JSON generated in

[GitHub] samza pull request #126: SAMZA-1182 : Disable flaky tests.

GitHub user shanthoosh opened a pull request: https://github.com/apache/samza/pull/126 SAMZA-1182 : Disable flaky tests. You can merge this pull request into a Git repository by running: $ git pull https://github.com/shanthoosh/samza disable_all_async_run_loop_tests

Re: Samza 0.12.0 artifact for scala 2.10 in maven central

Hi Jagadish, Thanks! Best regards, Maxim Logvinenko On 18 April 2017 at 21:29:11, Jagadish Venkatraman (jagadish1...@gmail.com) wrote: Hi Maksim, I published the artifacts. Please find the artifacts here For instance,

Re: [VOTE] Samza Logo

Oh, I already voted last week. I liked the orbital loop one the best:-) The dots appear to signify processor nodes, and the streams connect them. Also, it has a nice "S" like pattern aligning with Samza. Also, I did not like the "color blind" dots as much as the orbital loop :D On Tue, Apr 18,

Re: [VOTE] Samza Logo

Voted. I like the orbital one and the dotted 'S'. Red is not my preferred color, but Samza has been associated with red for a long time, so I don't see any reason for changing it. On Tue, Apr 18, 2017 at 11:38 AM, Navina Ramesh < nram...@linkedin.com.invalid> wrote: > @Renato: > Thanks for your

Re: [VOTE] Samza Logo

@Renato: Thanks for your feedback. Always appreciate help from our contributors :) @Jagadish: Thanks for stating your points. It is clear that you are against the butterfly ones. But are you in support of any of the others? Please vote :) Thanks! Navina On Tue, Apr 18, 2017 at 10:38 AM,

Re: Samza 0.12.0 artifact for scala 2.10 in maven central

Hi Maksim, I published the artifacts. Please find the artifacts here For instance, https://repository.apache.org/#nexus-search;quick~samza-core_2.10 Best, Jagadish On Mon, Apr 17,

Re: [VOTE] Samza Logo

FWIW, I have a contrarian perspective on this one. Here's my 2 cents: I'm -1 for having for our logo to do anything with a butterfly. - Samza and Kafka are separate top-level projects. I do not think the connection to Franz Kafka's novel on "metamorphosis", and the fact that a salesman named

Re: [VOTE] Samza Logo

Thanks for doing this Nacho! As a bit of an outsider I have to say that I have to agree with Jake. I really couldn't make the connection with the butterfly until I read it on the list. I also didn't get the one with only dots, I agree with Navina, it seemed like a color blind test ;) So for me the