on a site that I don't have account/access and it requires
> sign-up. Can you share it via google doc, since you have a gmail account?
> And just to confirm, you have upgrade and using 0.10.1 now, right?
>
> Thanks and apologize for the delay.
>
> -Yi
>
> On Fri, Sep 2,
Can any one help on this? Thanks!
On Thu, Sep 1, 2016 at 11:59 AM, 李斯宁 wrote:
> If you cannot see the attachment, please try http://note.youdao.com/
> noteshare?id=56b826c24af47a9fdb600490ce788710
>
> On Thu, Sep 1, 2016 at 1:50 AM, Chinmay Soman
> wrote:
>
>> Sorry
If you cannot see the attachment, please try
http://note.youdao.com/noteshare?id=56b826c24af47a9fdb600490ce788710
On Thu, Sep 1, 2016 at 1:50 AM, Chinmay Soman
wrote:
> Sorry dont see anything in the attachment. Can you please re-attach and
> re-send ?
>
> On Wed, Aug 31, 2016 at
It seems upgrading does not solve the problem. All task hang in today's
"rush hour".
I attached log and jstack.
The SAMZA-911 want to fix by stopping the process if failed too much
times. But the process is still there and hanging.
On Mon, Aug 22, 2016 at 1:14 PM, 李斯宁 wrote:
&
Thanks so much, I'll try.
On Mon, Aug 22, 2016 at 6:26 AM, Yi Pan wrote:
> Hi, Sining,
>
> This is a known bug that is fixed in 0.10.1 (SAMZA-911). Please try to
> upgrade to 0.10.1.
>
> Thanks!
>
> -Yi
>
> On Sun, Aug 21, 2016 at 5:55 AM, 李斯宁 wrote:
>
nd metrics writing method
do not recognize that and retry again and again?
Any response is appreciated :)
On Sun, Aug 21, 2016 at 8:00 PM, 李斯宁 wrote:
> at the last of the container's log, prints these:
>
> 2016-08-21 19:57:01 [WARN ](o.a.s.s.k.KafkaSystemProducer :66 ) Retrying
ption -
org.apache.kafka.common.errors.NotLeaderForPartitionException: This
server is not the leader for that topic-partition.. Turn on debugging
to get a full stack trace
On Sun, Aug 21, 2016 at 7:38 PM, 李斯宁 wrote:
> hi, guys
> I'm using samza in realtime process. After running for about 10 hours,
&
hi, guys
I'm using samza in realtime process. After running for about 10 hours, some
containers paused and not processing.
When I looked into the log, I found a lot of
2016-08-21 10:03:07 [WARN ](o.a.k.c.p.i.Sender :257)
Got error produce response with correlation id 490345 on
top
lso an important metric, which is
> named kafka-*-*-messages-behind-high-watermark.
>
> You will need to take a peek at the published JSON to get a sense of what
> metrics are reported.
>
> Thanks,
> David
>
>
>
> On Mon, Aug 8, 2016 at 12:50 AM 李斯宁 wrote:
>
>
eed to click to view every container's log or connect to every
container's jmxport to get information.
I already found that we can do some monitoring from 'coordinate' and
'checkpoint' streams, but
is there a tool available for such monitoring requirement? I think it is a
very common need.
--
李斯宁
serid-db may not be partitioned the same way as you expect to
> consume in your Samza job.
> 3) The location of a specific partition of your userid-db in a Samza job is
> dynamically allocated as YARN schedules the containers in the cluster.
> Hence, where to copy the offline data over is n
rid-db data,
and I don't want to process long history log to build the userid-db from
empty. So I need to import userid-db from my old batch processing system.
any reply is appreciated, thanks in advance.
--
李斯宁
12 matches
Mail list logo
