Re: No Metrics Emitted in new High-Level API

2018-01-26 Thread Yi Pan
Hi, Srujun, I noticed that you did not configure the metrics serde as stated here: http://samza.apache.org/learn/documentation/0.14/container/metrics.html. Could that be the reason? -Yi On Fri, Jan 26, 2018 at 7:58 PM, Jagadish Venkatraman < jagadish1...@gmail.com> wrote: > Can you turn on DEBU

Re: No Metrics Emitted in new High-Level API

2018-01-26 Thread Jagadish Venkatraman
Can you turn on DEBUG logging for the MetricsSnapshotReporter class and re-attach the logs? I cannot observe any obvious red-flag from your logs. On Fri, Jan 26, 2018 at 7:13 PM, Srujun Thanmay Gupta wrote: > Hello Yi, > > The logs are less than 100KB each, I'm not sure if that's too large for t

Re: No Metrics Emitted in new High-Level API

2018-01-26 Thread Srujun Thanmay Gupta
Hello Yi, The logs are less than 100KB each, I'm not sure if that's too large for the mailing list system. I've uploaded the log files to the links below, in case others would like to look at them too. http://srujun.com/files/samza/wikipedia-application_samza-container-0.log http://srujun.com/fil

Re: No Metrics Emitted in new High-Level API

2018-01-26 Thread Yi Pan
Hi, Srujun, I did not see the container logs in the attachment. Is it too big? Can you send it to my personal email yi...@linkedin.com? Thanks! -Yi On Fri, Jan 26, 2018 at 5:23 PM, Srujun Thanmay Gupta wrote: > Hello, > > I have attached the container log and the job coordinator logs for the

Re: No Metrics Emitted in new High-Level API

2018-01-26 Thread Srujun Thanmay Gupta
Hello, I have attached the container log and the job coordinator logs for the two samples I ran, and the .properties configuration files used. The wikipedia-feed and wikipedia-application code are exactly the same as in the master branch on hello-samza. The only change is that I added the metrics

[GitHub] samza pull request #416: SAMZA-1568: Handle ZkInterruptedException in zkclie...

2018-01-26 Thread shanthoosh
GitHub user shanthoosh opened a pull request: https://github.com/apache/samza/pull/416 SAMZA-1568: Handle ZkInterruptedException in zkclient.close. When zookeeper session failures occur in a stream processor, leaves the group(zkClient is closed) and joins the group again.

Re: No Metrics Emitted in new High-Level API

2018-01-26 Thread Jagadish Venkatraman
Hi Srujun, Metrics reporting should be supported independent of the deployment model. Can you please attach your container log file? Are you seeing log lines from MetricsSnapshotReporter: https://github.com/apache/samza/blob/master/samza-core/src/main/scala/org/apache/samza/metrics/reporter/Metri

No Metrics Emitted in new High-Level API

2018-01-26 Thread Srujun Thanmay Gupta
Hello, I am trying to get metrics from my sample Samza application into Kafka. My application uses the new high-level API and I am expecting to see the default Samza metrics in the "metrics" topic within Kafka. I have configured the stream based on the Metrics Documentation on the Samza website (h

SEP-11. Host Affinity in standalone discussion.

2018-01-26 Thread Boris S
Shanthoosh, Thank you for suggesting and submitting this SEP: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=75957309 Couple of things I would want to point out so far: 1. Kudos on cleaning up the interface and introducing new ones (LocalityInfo and LocalityManager). I t

[GitHub] samza pull request #415: SAMZA-1578: Fix watermark bug found by BEAM tests

2018-01-26 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/samza/pull/415 ---

[GitHub] samza pull request #415: SAMZA-1578: Fix watermark bug found by BEAM tests

2018-01-26 Thread xinyuiscool
GitHub user xinyuiscool opened a pull request: https://github.com/apache/samza/pull/415 SAMZA-1578: Fix watermark bug found by BEAM tests The problem is getOutputWatermark() does not return the real outputWatermark. This caused problem in user override watermark function. You can m

[GitHub] samza pull request #414: Added some logging to stdout for easier parsing by ...

2018-01-26 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/samza/pull/414 ---

[GitHub] samza pull request #414: Added some logging to stdout for easier parsing by ...

2018-01-26 Thread prateekm
GitHub user prateekm opened a pull request: https://github.com/apache/samza/pull/414 Added some logging to stdout for easier parsing by tools. You can merge this pull request into a Git repository by running: $ git pull https://github.com/prateekm/samza print-container-info A