Pengwei created KAFKA-7411:
--
Summary: Change system to future and change back will make
replication not working
Key: KAFKA-7411
URL: https://issues.apache.org/jira/browse/KAFKA-7411
Project: Kafka
Pengwei created KAFKA-5425:
--
Summary: Kafka replication support all log segment files sync with
leader
Key: KAFKA-5425
URL: https://issues.apache.org/jira/browse/KAFKA-5425
Project: Kafka
Issue Typ
Pengwei created KAFKA-5480:
--
Summary: Partition Leader may not be elected although there is one
live replica in ISR
Key: KAFKA-5480
URL: https://issues.apache.org/jira/browse/KAFKA-5480
Project: Kafka
Pengwei created KAFKA-5553:
--
Summary: Delete topic failed to change from OnlineReplica to
ReplicaDeletionStarted if ISR not created
Key: KAFKA-5553
URL: https://issues.apache.org/jira/browse/KAFKA-5553
Proj
Pengwei created KAFKA-5752:
--
Summary: Delete topic and re-create topic immediate will delete
the new topic's timeindex
Key: KAFKA-5752
URL: https://issues.apache.org/jira/browse/KAFKA-5752
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15331523#comment-15331523
]
Pengwei commented on KAFKA-1429:
I can still reproduce this issue in 0.9.0.0 or 0.9.0.1,
[
https://issues.apache.org/jira/browse/KAFKA-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pengwei updated KAFKA-1429:
---
Attachment: kafka_0.9.0.0_controller_dead_lock.patch
upload file is the patch to fix this bug, can somebody re
Pengwei created KAFKA-3913:
--
Summary: Old consumer's metrics error when using IPv6
Key: KAFKA-3913
URL: https://issues.apache.org/jira/browse/KAFKA-3913
Project: Kafka
Issue Type: Bug
Com
[
https://issues.apache.org/jira/browse/KAFKA-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15390887#comment-15390887
]
Pengwei commented on KAFKA-1429:
hi Jun, I have open a PR for this issue. Can you review i
[
https://issues.apache.org/jira/browse/KAFKA-4229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15698992#comment-15698992
]
Pengwei commented on KAFKA-4229:
The PR is : https://github.com/apache/kafka/pull/2175
>
[
https://issues.apache.org/jira/browse/KAFKA-4229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pengwei updated KAFKA-4229:
---
Reviewer: Guozhang Wang
> Controller can't start after several zk expired event
>
[
https://issues.apache.org/jira/browse/KAFKA-4229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on KAFKA-4229 started by Pengwei.
--
> Controller can't start after several zk expired event
> ---
[
https://issues.apache.org/jira/browse/KAFKA-4229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pengwei updated KAFKA-4229:
---
Status: Patch Available (was: In Progress)
PR : https://github.com/apache/kafka/pull/2175
> Controller can't
Pengwei created KAFKA-4790:
--
Summary: Kafka can't not recover after a disk full
Key: KAFKA-4790
URL: https://issues.apache.org/jira/browse/KAFKA-4790
Project: Kafka
Issue Type: Bug
Affects Versi
[
https://issues.apache.org/jira/browse/KAFKA-4790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15880567#comment-15880567
]
Pengwei commented on KAFKA-4790:
The index max file set to 1MB
log.index.size.max.bytes=10
Pengwei created KAFKA-4862:
--
Summary: Kafka client connect to a shutdown node will block for a
long time
Key: KAFKA-4862
URL: https://issues.apache.org/jira/browse/KAFKA-4862
Project: Kafka
Issue T
[
https://issues.apache.org/jira/browse/KAFKA-4790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15904333#comment-15904333
]
Pengwei commented on KAFKA-4790:
[~junrao] If KIP-98 can fix this issue, we can wait for t
[
https://issues.apache.org/jira/browse/KAFKA-4790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15904333#comment-15904333
]
Pengwei edited comment on KAFKA-4790 at 3/10/17 10:54 AM:
--
[~junr
Pengwei created KAFKA-5014:
--
Summary: SSL Channel not ready but tcp is established and the
server is hung will not sending metadata
Key: KAFKA-5014
URL: https://issues.apache.org/jira/browse/KAFKA-5014
Proje
[
https://issues.apache.org/jira/browse/KAFKA-4862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pengwei updated KAFKA-4862:
---
Status: Patch Available (was: Open)
> Kafka client connect to a shutdown node will block for a long time
> --
Pengwei created KAFKA-4595:
--
Summary: Controller send thread can't stop when broker change
listener event trigger for dead brokers
Key: KAFKA-4595
URL: https://issues.apache.org/jira/browse/KAFKA-4595
Proje
[
https://issues.apache.org/jira/browse/KAFKA-4595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15801343#comment-15801343
]
Pengwei commented on KAFKA-4595:
The broker change event is trigger to remove dead brokers
[
https://issues.apache.org/jira/browse/KAFKA-4595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15803812#comment-15803812
]
Pengwei commented on KAFKA-4595:
Yes, you are right.
> Controller send thread can't stop
[
https://issues.apache.org/jira/browse/KAFKA-4595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15803816#comment-15803816
]
Pengwei commented on KAFKA-4595:
[~huxi_2b]
> Controller send thread can't stop when brok
[
https://issues.apache.org/jira/browse/KAFKA-4595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15811007#comment-15811007
]
Pengwei commented on KAFKA-4595:
One method is to add a lock timeout method instead of blo
[
https://issues.apache.org/jira/browse/KAFKA-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15817467#comment-15817467
]
Pengwei commented on KAFKA-3042:
[~lindong] It seems I still encounter this issue after a
[
https://issues.apache.org/jira/browse/KAFKA-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pengwei reopened KAFKA-3042:
> updateIsr should stop after failed several times due to zkVersion issue
>
[
https://issues.apache.org/jira/browse/KAFKA-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15817467#comment-15817467
]
Pengwei edited comment on KAFKA-3042 at 1/11/17 7:27 AM:
-
[~lindon
Pengwei created KAFKA-3562:
--
Summary: Null Pointer Exception Found when delete topic and Using
New Producer
Key: KAFKA-3562
URL: https://issues.apache.org/jira/browse/KAFKA-3562
Project: Kafka
Issu
Pengwei created KAFKA-3584:
--
Summary: NullPointer Exception found when Delete Topic and Log
delete concurrent
Key: KAFKA-3584
URL: https://issues.apache.org/jira/browse/KAFKA-3584
Project: Kafka
Is
Pengwei created KAFKA-3585:
--
Summary: Shutdown slow when there is only one broker which is
controller
Key: KAFKA-3585
URL: https://issues.apache.org/jira/browse/KAFKA-3585
Project: Kafka
Issue Type
[
https://issues.apache.org/jira/browse/KAFKA-3585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15268171#comment-15268171
]
Pengwei commented on KAFKA-3585:
Is the last broker become the controller ?
I can repro
[
https://issues.apache.org/jira/browse/KAFKA-3585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15275880#comment-15275880
]
Pengwei commented on KAFKA-3585:
do you used the kafka-server-stop.sh to shutdown?
> Shut
[
https://issues.apache.org/jira/browse/KAFKA-3585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pengwei updated KAFKA-3585:
---
Comment: was deleted
(was: do you used the kafka-server-stop.sh to shutdown?)
> Shutdown slow when there is o
[
https://issues.apache.org/jira/browse/KAFKA-3585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15275879#comment-15275879
]
Pengwei commented on KAFKA-3585:
do you used the kafka-server-stop.sh to shutdown?
> Shut
[
https://issues.apache.org/jira/browse/KAFKA-2903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15046561#comment-15046561
]
Pengwei commented on KAFKA-2903:
Yes we can also add comment on it.
But if in the future
Pengwei created KAFKA-2995:
--
Summary: in 0.9.0.0 Old Consumer's commitOffsets with specify
partition can submit not exists topic and partition to zk
Key: KAFKA-2995
URL: https://issues.apache.org/jira/browse/KAFKA-2995
Pengwei created KAFKA-3075:
--
Summary: java.util.HashMap cannot be cast to
scala.collection.immutable.Map When using
ZookeeperConsumerConnector.commitOffsets
Key: KAFKA-3075
URL: https://issues.apache.org/jira/browse/KA
[
https://issues.apache.org/jira/browse/KAFKA-3075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pengwei updated KAFKA-3075:
---
Description:
When using java api's commit offset :
public void commitOffsets(Map
offsetsToCommit, boolean r
[
https://issues.apache.org/jira/browse/KAFKA-3075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pengwei updated KAFKA-3075:
---
Description:
When using java api's commit offset :
public void commitOffsets(Map
offsetsToCommit, boolean r
Pengwei created KAFKA-4229:
--
Summary: Controller can't start after serveral zk expired event
Key: KAFKA-4229
URL: https://issues.apache.org/jira/browse/KAFKA-4229
Project: Kafka
Issue Type: Bug
[
https://issues.apache.org/jira/browse/KAFKA-4229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pengwei updated KAFKA-4229:
---
Fix Version/s: (was: 0.10.1.0)
> Controller can't start after serveral zk expired event
>
[
https://issues.apache.org/jira/browse/KAFKA-4229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pengwei updated KAFKA-4229:
---
Fix Version/s: 0.10.1.0
> Controller can't start after serveral zk expired event
> ---
[
https://issues.apache.org/jira/browse/KAFKA-4229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15532241#comment-15532241
]
Pengwei commented on KAFKA-4229:
I already have a patch for this issue, maybe the issue ca
[
https://issues.apache.org/jira/browse/KAFKA-4229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pengwei updated KAFKA-4229:
---
Summary: Controller can't start after several zk expired event (was:
Controller can't start after serveral zk
[
https://issues.apache.org/jira/browse/KAFKA-4229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pengwei updated KAFKA-4229:
---
Description:
We found the controller not started after several zk expired event in our test
environment. By
[
https://issues.apache.org/jira/browse/KAFKA-4229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15571265#comment-15571265
]
Pengwei commented on KAFKA-4229:
We test it on 0.9.0.0, but I found the controller code ar
Pengwei created KAFKA-2903:
--
Summary: FileMessageSet's read method maybe has problem when start
is not zero
Key: KAFKA-2903
URL: https://issues.apache.org/jira/browse/KAFKA-2903
Project: Kafka
Issu
[
https://issues.apache.org/jira/browse/KAFKA-2903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pengwei updated KAFKA-2903:
---
Affects Version/s: 0.9.0.0
0.8.2.1
Fix Version/s: 0.9.0.0
> FileMessageSet's re
49 matches
Mail list logo
