Wang,
That did it. Thanks a lot.
- Shekar
On Thu, May 14, 2015 at 10:38 AM, Guozhang Wang wrote:
> Hi Shekar,
>
> It seems the incoming / outgoing topics are not the root of the problem
> here, but the checkpoint topic "__samza_checkpoint_ver_1_for_Argos". From
> the error logs this topic onl
Hi Shekar,
It seems the incoming / outgoing topics are not the root of the problem
here, but the checkpoint topic "__samza_checkpoint_ver_1_for_Argos". From
the error logs this topic only has one replica 1018019532, which was down
and hence not available.
Guozhang
On Thu, May 14, 2015 at 5:16 AM
Here is what I see on Kafka log:
[2015-05-14 04:11:27,752] ERROR Closing socket for /10.180.195.32 because
of error (kafka.network.Processor)
java.io.IOException: Connection reset by peer
at sun.nio.ch.FileDispatcherImpl.read0(Native Method)
at sun.nio.ch.SocketDispatcher.read(S
Here is the complete log:
http://pastebin.com/nX7twETm
Interesting, I see a leader not available exception instead of the earlier
one.
./container_1431601903660_0001_01_02/samza-container-0.log:2015-05-14
04:53:41 BrokerPartitionInfo [WARN] Error while fetching metadata partition
0 leader: n
Hey Shekar,
Can you paste the entire stacktrace/log? Where there any other errors ?
On Wed, May 13, 2015 at 6:04 PM Shekar Tippur wrote:
> Hello,
>
> I seem to come across a issue with replication. We have 2 nodes where Kafka
> and yarn run.
>
> We have enabled replication factor on Kafka (Replic
