Hi,
We are getting the error i've pasted at the bottom of the mail in a Samza
task, it never recovers and keeps printing messages like this in the log:
2016-07-27 17:46:20 BrokerProxy [DEBUG] Removed [event,1]
2016-07-27 17:46:20 KafkaSystemConsumer [INFO] Abdicating for [event,1]
2016-07-27 17:4
Hi Everyone,
Does anyone run Samza 0.10 with Kafka 0.9.0.0?
Is this a stable configuration?
Thanks,
Michael
inspecting on the consumer end.
> -Jordan
>
> On Mon, Nov 16, 2015 at 9:16 AM, Michael Ravits
> wrote:
>
> > Hi,
> >
> > I'd like to monitor consumer's lag.
> > Found this tool https://github.com/linkedin/Burrow.
> > But now realized that Samza
Hi,
I'd like to monitor consumer's lag.
Found this tool https://github.com/linkedin/Burrow.
But now realized that Samza is using it's own checkpointing mechanism.
So question is what's the best way to monitor whether and how much the
consumer is lagging?
On a related subject, I'd also like to mo
less memory is needed) with ThreadJobFactory.
>
> One downside was that the logger wouldn't respect the lib/log4j.xml
> configuration file anymore, but that's probably some error on my part.
>
> Lukas
>
> On Sat, May 30, 2015 at 2:41 PM, Michael Ravits
> wrote:
&g
Hi Lukas,
We use similar docker based deployment.
Would be glad if you could post here if ThreadJobFactory worked well for
you.
Thanks,
Michael
On Sat, May 30, 2015 at 12:22 AM, Lukas Steiblys
wrote:
> Yes, I think switching to ThreadJobFactory is a good solution. I think the
> reasons why I s
t 1 partition. So there will be 500 processes working
> through the log.
>
> I'd try to figure out what your scaling needs are for the next 2-3 years
> and then calculate your resource requirements accordingly (how many
> parallel executing tasks you would need). If yo
ur system processing 100 messages/s and there's plenty of
> room to grow.
>
> Lukas
>
> On Thursday, May 21, 2015, Michael Ravits wrote:
>
> > Hi,
> >
> > I wonder what are the considerations I need to account for in regard to
> the
> > number of pa
Hi,
I wonder what are the considerations I need to account for in regard to the
number of partitions in input topics for Samza.
When testing with a 500 partitions topic with one Samza job I noticed the
start up time to be very long.
Are there any problems that might occur when dealing with this nu
which means void actually returns something
else?
Sincerely,
Michael
On Mon, May 18, 2015 at 4:21 PM, Gustavo Anatoly
wrote:
> Hi, Michael Ravits.
>
> The error happens when the Log class try to read the
> jetty-logging.properties file. Please take a
which means void actually returns something
else?
Sincerely,
Michael
On Mon, May 18, 2015 at 4:21 PM, Gustavo Anatoly
wrote:
> Hi, Michael Ravits.
>
> The error happens when the Log class try to read the
> jetty-logging.properties file. Please take a
Hi Everybody,
Trying to get up and running with a Clojure Samza Task.
I think that my question is Clojure specific but I guess that some of the
folks here are Clojure developers which might also know the answers.
I'm trying to run a job, using the same code as here:
https://github.com/apache/samz
12 matches
Mail list logo
