gt;
> We recently discovered an issue in Kafka 0.9.0.1 (), where
> ReplicaFetcherThread stopped after ReplicaFetcherThread received a corrupted
> message. As the same logic exists also in Kafka 0.10.0.0 and 0.10.0.1, they
> may have the similar issue.
> Here are system logs related to
)
Issue resolved by pull request 2127
[https://github.com/apache/kafka/pull/2127]
> ReplicaFetcherThread stopped after ReplicaFetcherThread received a corrupted
> message
>
>
>
uest at:
https://github.com/apache/kafka/pull/2127
> ReplicaFetcherThread stopped after ReplicaFetcherThread received a corrupted
> message
>
>
> Key: KAFKA-4384
>
lose.
> ReplicaFetcherThread stopped after ReplicaFetcherThread received a corrupted
> message
>
>
> Key: KAFKA-4384
> URL: https://issues.apache.org/jira/browse/KAFKA-4384
>
d be in 0.10.1.1?
> ReplicaFetcherThread stopped after ReplicaFetcherThread received a corrupted
> message
>
>
> Key: KAFKA-4384
> URL: https://issues.apache.org/
pull/2127). Thanks.
> ReplicaFetcherThread stopped after ReplicaFetcherThread received a corrupted
> message
>
>
> Key: KAFKA-4384
> URL: https://issues.apache
uest:
https://github.com/apache/kafka/pull/2127
KAFKA-4384: ReplicaFetcherThread stopped after ReplicaFetcherThread
received a corrupted message
@becketqin
Here is the patch for KAFKA-4384 (ReplicaFetcherThread stopped after
ReplicaFetcherThread received a corrupted mes
gt; > the ReplicaFetcherThread class, to reset the fetching offset to the log
> > end
> > > offset of the leader and then retry. So I do not know why you observed
> > that
> > > the thread actually stopped because of this issue. Could you check the
> > > source code as wel
erThread class, to reset the fetching offset to the log
> end
> > offset of the leader and then retry. So I do not know why you observed
> that
> > the thread actually stopped because of this issue. Could you check the
> > source code as well as stack trace to see why th
un
On Wed, Nov 2, 2016 at 1:38 AM, Jun H. wrote:
> Hi all,
>
> We recently discovered an issue in Kafka 0.9.0.1 (), where
> ReplicaFetcherThread stopped after ReplicaFetcherThread received a
> corrupted message. As the same logic exists also in Kafka 0.10.0.0 and
> 0.10.0.1, the
H. wrote:
>
> > Hi all,
> >
> > We recently discovered an issue in Kafka 0.9.0.1 (), where
> > ReplicaFetcherThread stopped after ReplicaFetcherThread received a
> > corrupted message. As the same logic exists also in Kafka 0.10.0.0 and
> > 0.10.0.1, they may have the s
We recently discovered an issue in Kafka 0.9.0.1 (), where
> ReplicaFetcherThread stopped after ReplicaFetcherThread received a corrupted
> message. As the same logic exists also in Kafka 0.10.0.0 and 0.10.0.1, they
> may have the similar issue.
> Here are system logs related to this issu
g an unit test, please let
me know if there is anything else I should do. Thanks.
> ReplicaFetcherThread stopped after ReplicaFetcherThread received a corrupted
> message
>
>
>
received a corrupted message)
)
> ReplicaFetcherThread stopped after ReplicaFetcherThread received a corrupted
> message
>
>
> Key: KAFKA-4384
> URL: https://issu
: Open)
Patch for KAFKA-4384 (ReplicaFetcherThread stopped after ReplicaFetcherThread
received a corrupted message)
> ReplicaFetcherThread stopped after ReplicaFetcherThread received a corrupted
> m
received a corrupted message)
> ReplicaFetcherThread stopped after ReplicaFetcherThread received a corrupted
> message
>
>
> Key: KAFKA-4384
> URL: https://issu
urce code as well as stack trace to see why this happens?
Guozhang
On Wed, Nov 2, 2016 at 4:38 AM, Jun H. wrote:
> Hi all,
>
> We recently discovered an issue in Kafka 0.9.0.1 (), where
> ReplicaFetcherThread stopped after ReplicaFetcherThread received a
> corrupted message. As
[
https://issues.apache.org/jira/browse/KAFKA-4384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-4384:
---
Fix Version/s: 0.10.1.1
> ReplicaFetcherThread stopped after ReplicaFetcherThread receive
will provide the patch
soon.
> ReplicaFetcherThread stopped after ReplicaFetcherThread received a corrupted
> message
>
>
> Key: KAFKA-4384
> URL: https://issues.
Yes, this looks a bug and the fix plan
sounds good to me. Would you provide a patch?
> ReplicaFetcherThread stopped after ReplicaFetcherThread received a corrupted
> message
>
>
>
Jun He created KAFKA-4384:
-
Summary: ReplicaFetcherThread stopped after ReplicaFetcherThread
received a corrupted message
Key: KAFKA-4384
URL: https://issues.apache.org/jira/browse/KAFKA-4384
Project: Kafka
Hi all,
We recently discovered an issue in Kafka 0.9.0.1 (), where
ReplicaFetcherThread stopped after ReplicaFetcherThread received a
corrupted message. As the same logic exists also in Kafka 0.10.0.0 and
0.10.0.1, they may have the similar issue.
Here are system logs related to this issue
22 matches
Mail list logo
