ChenLin created KAFKA-8328:
--
Summary: Kafka smooth expansion
Key: KAFKA-8328
URL: https://issues.apache.org/jira/browse/KAFKA-8328
Project: Kafka
Issue Type: Improvement
Components: client
[
https://issues.apache.org/jira/browse/KAFKA-8328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8328:
---
Description:
When expanding the kafka cluster, the new follower will read the data from the
earliest offset.
[
https://issues.apache.org/jira/browse/KAFKA-8328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8328:
---
Attachment: Kafka_smooth_expansion.patch
> Kafka smooth expansion
> --
>
>
[
https://issues.apache.org/jira/browse/KAFKA-8328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8328:
---
Description:
When expanding the kafka cluster, the new follower will read the data from the
earliest offset.
[
https://issues.apache.org/jira/browse/KAFKA-8328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8328:
---
Attachment: (was: image-2019-05-07-15-05-46-641.png)
> Kafka smooth expansion
> --
>
[
https://issues.apache.org/jira/browse/KAFKA-8328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8328:
---
Description:
When expanding the kafka cluster, the new follower will read the data from the
earliest offset.
[
https://issues.apache.org/jira/browse/KAFKA-8328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8328:
---
Description:
When expanding the kafka cluster, the new follower will read the data from the
earliest offset.
[
https://issues.apache.org/jira/browse/KAFKA-8328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8328:
---
Flags: Patch (was: Patch,Important)
> Kafka smooth expansion
> --
>
> Ke
[
https://issues.apache.org/jira/browse/KAFKA-8328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8328:
---
Description:
When expanding the kafka cluster, the new follower will read the data from the
earliest offset.
[
https://issues.apache.org/jira/browse/KAFKA-8328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8328:
---
Attachment: image-2019-05-07-15-05-46-641.png
> Kafka smooth expansion
> --
>
>
ChenLin created KAFKA-8465:
--
Summary: Copying strategy for the topic dimension
Key: KAFKA-8465
URL: https://issues.apache.org/jira/browse/KAFKA-8465
Project: Kafka
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/KAFKA-8465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8465:
---
Attachment: Copying_strategy_for_the_topic_dimension.patch
> Copying strategy for the topic dimension
> -
[
https://issues.apache.org/jira/browse/KAFKA-8465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8465:
---
Attachment: (was: Copying_strategy_for_the_topic_dimension.patch)
> Copying strategy for the topic dimens
[
https://issues.apache.org/jira/browse/KAFKA-8465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8465:
---
Attachment: replication__strategy_for_the_topic_dimension.patch
> Copying strategy for the topic dimension
>
[
https://issues.apache.org/jira/browse/KAFKA-8328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16854411#comment-16854411
]
ChenLin commented on KAFKA-8328:
Thank you for your attention, I will submit KIP as soon
[
https://issues.apache.org/jira/browse/KAFKA-8328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16865488#comment-16865488
]
ChenLin commented on KAFKA-8328:
[~Yohan123]
look forward to your reply，KIP
url:[https:
[
https://issues.apache.org/jira/browse/KAFKA-8328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17168514#comment-17168514
]
ChenLin commented on KAFKA-8328:
Thanks for your attention, I will re submit the batch to
[
https://issues.apache.org/jira/browse/KAFKA-8328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17168515#comment-17168515
]
ChenLin commented on KAFKA-8328:
Thanks for your attention, I will re submit the batch to
ChenLin created KAFKA-8722:
--
Summary: In some cases, the crc check does not cause dirty data to
be written.
Key: KAFKA-8722
URL: https://issues.apache.org/jira/browse/KAFKA-8722
Project: Kafka
Issu
[
https://issues.apache.org/jira/browse/KAFKA-8722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8722:
---
Attachment: image-2019-07-27-14-50-08-128.png
> In some cases, the crc check does not cause dirty data to be
[
https://issues.apache.org/jira/browse/KAFKA-8722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8722:
---
Attachment: image-2019-07-27-14-50-58-300.png
> In some cases, the crc check does not cause dirty data to be
[
https://issues.apache.org/jira/browse/KAFKA-8722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8722:
---
Description:
In our production environment, when we consume kafka's topic data in an
operating program, we f
[
https://issues.apache.org/jira/browse/KAFKA-8722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8722:
---
Attachment: image-2019-07-27-14-56-25-610.png
> In some cases, the crc check does not cause dirty data to be
[
https://issues.apache.org/jira/browse/KAFKA-8722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8722:
---
Attachment: image-2019-07-27-14-57-06-687.png
> In some cases, the crc check does not cause dirty data to be
[
https://issues.apache.org/jira/browse/KAFKA-8722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8722:
---
Attachment: image-2019-07-27-15-00-14-673.png
> In some cases, the crc check does not cause dirty data to be
[
https://issues.apache.org/jira/browse/KAFKA-8722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8722:
---
Attachment: image-2019-07-27-15-05-12-565.png
> In some cases, the crc check does not cause dirty data to be
[
https://issues.apache.org/jira/browse/KAFKA-8722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8722:
---
Attachment: image-2019-07-27-15-06-07-123.png
> In some cases, the crc check does not cause dirty data to be
[
https://issues.apache.org/jira/browse/KAFKA-8722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8722:
---
Attachment: image-2019-07-27-15-10-21-709.png
> In some cases, the crc check does not cause dirty data to be
[
https://issues.apache.org/jira/browse/KAFKA-8722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8722:
---
Description:
In our production environment, when we consume kafka's topic data in an
operating program, we f
[
https://issues.apache.org/jira/browse/KAFKA-8722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8722:
---
Attachment: image-2019-07-27-15-18-22-716.png
> In some cases, the crc check does not cause dirty data to be
[
https://issues.apache.org/jira/browse/KAFKA-8722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8722:
---
Description:
In our production environment, when we consume kafka's topic data in an
operating program, we f
[
https://issues.apache.org/jira/browse/KAFKA-8722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8722:
---
Attachment: Crc_data_verification_repair.patch
> In some cases, the crc check does not cause dirty data to be
[
https://issues.apache.org/jira/browse/KAFKA-8722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8722:
---
Description:
In our production environment, when we consume kafka's topic data in an
operating program, we f
[
https://issues.apache.org/jira/browse/KAFKA-8722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8722:
---
Attachment: (was: Crc_data_verification_repair.patch)
> In some cases, the crc check does not cause dirty
[
https://issues.apache.org/jira/browse/KAFKA-8722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8722:
---
Attachment: (was: image-2019-07-27-15-00-14-673.png)
> In some cases, the crc check does not cause dirty
[
https://issues.apache.org/jira/browse/KAFKA-8722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8722:
---
Description:
In our production environment, when we consume kafka's topic data in an
operating program, we f
[
https://issues.apache.org/jira/browse/KAFKA-8722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8722:
---
Attachment: image-2019-07-30-11-39-01-605.png
> In some cases, the crc check does not cause dirty data to be
[
https://issues.apache.org/jira/browse/KAFKA-8722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8722:
---
Summary: Data crc check repair (was: In some cases, the crc check does not
cause dirty data to be written.)
[
https://issues.apache.org/jira/browse/KAFKA-8465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8465:
---
Attachment: (was: replication__strategy_for_the_topic_dimension.patch)
> Copying strategy for the topic d
[
https://issues.apache.org/jira/browse/KAFKA-8465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8465:
---
Attachment: replication_strategy_for_the_topic_dimension.patch
> Copying strategy for the topic dimension
> -
[
https://issues.apache.org/jira/browse/KAFKA-8465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8465:
---
Description:
When some partiton's replication is assigned to a broker, which disks should
these copies be pl
[
https://issues.apache.org/jira/browse/KAFKA-8465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8465:
---
Attachment: image-2019-07-30-13-35-30-126.png
> Copying strategy for the topic dimension
> --
[
https://issues.apache.org/jira/browse/KAFKA-8465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8465:
---
Attachment: image-2019-07-30-13-35-58-872.png
> Copying strategy for the topic dimension
> --
[
https://issues.apache.org/jira/browse/KAFKA-8465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8465:
---
Attachment: (was: image-2019-07-30-13-35-30-126.png)
> Copying strategy for the topic dimension
> ---
[
https://issues.apache.org/jira/browse/KAFKA-8465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8465:
---
Attachment: image-2019-07-30-13-38-21-015.png
> Copying strategy for the topic dimension
> --
[
https://issues.apache.org/jira/browse/KAFKA-8465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8465:
---
Attachment: (was: image-2019-07-30-13-35-58-872.png)
> Copying strategy for the topic dimension
> ---
[
https://issues.apache.org/jira/browse/KAFKA-8465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8465:
---
Attachment: (was: image-2019-07-30-13-38-21-015.png)
> Copying strategy for the topic dimension
> ---
[
https://issues.apache.org/jira/browse/KAFKA-8465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8465:
---
Attachment: image-2019-07-30-13-40-49-878.png
> Copying strategy for the topic dimension
> --
[
https://issues.apache.org/jira/browse/KAFKA-8465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8465:
---
Attachment: image-2019-07-30-13-40-12-711.png
> Copying strategy for the topic dimension
> --
[
https://issues.apache.org/jira/browse/KAFKA-8465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8465:
---
Description:
When some partiton's replication is assigned to a broker, which disks should
these copies be pl
[
https://issues.apache.org/jira/browse/KAFKA-8465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8465:
---
Summary: Make sure that the copy of the same topic is evenly distributed
across a broker's disk. (was: Copyi
ChenLin created KAFKA-8832:
--
Summary: We should limit the maximum size read by a fetch request
on the kafka server.
Key: KAFKA-8832
URL: https://issues.apache.org/jira/browse/KAFKA-8832
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-8832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8832:
---
Attachment: image-2019-08-25-15-31-56-707.png
> We should limit the maximum size read by a fetch request on t
[
https://issues.apache.org/jira/browse/KAFKA-8832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8832:
---
Description:
I found that kafka is not on the server side, limiting the amount of data read
per fetch reques
[
https://issues.apache.org/jira/browse/KAFKA-8832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8832:
---
Description:
I found that kafka is not on the server side, limiting the amount of data read
per fetch reques
[
https://issues.apache.org/jira/browse/KAFKA-8832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8832:
---
Description:
I found that kafka is not on the server side, limiting the amount of data read
per fetch reques
[
https://issues.apache.org/jira/browse/KAFKA-8832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8832:
---
Attachment: image-2019-08-25-15-42-24-379.png
> We should limit the maximum size read by a fetch request on t
[
https://issues.apache.org/jira/browse/KAFKA-8832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8832:
---
Description:
I found that kafka is not on the server side, limiting the amount of data read
per fetch reques
[
https://issues.apache.org/jira/browse/KAFKA-8832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8832:
---
Attachment: image-2019-08-29-11-01-17-347.png
> We should limit the maximum size read by a fetch request on t
[
https://issues.apache.org/jira/browse/KAFKA-8832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8832:
---
Attachment: image-2019-08-29-11-01-04-147.png
> We should limit the maximum size read by a fetch request on t
[
https://issues.apache.org/jira/browse/KAFKA-8832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8832:
---
Description:
I found that kafka is not on the server side, limiting the amount of data read
per fetch reques
[
https://issues.apache.org/jira/browse/KAFKA-8832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8832:
---
Attachment: image-2019-08-29-11-02-01-477.png
> We should limit the maximum size read by a fetch request on t
[
https://issues.apache.org/jira/browse/KAFKA-8832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8832:
---
Description:
I found that kafka is not on the server side, limiting the amount of data read
per fetch reques
[
https://issues.apache.org/jira/browse/KAFKA-8832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8832:
---
Attachment: image-2019-08-29-11-03-37-693.png
> We should limit the maximum size read by a fetch request on t
[
https://issues.apache.org/jira/browse/KAFKA-8832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16918238#comment-16918238
]
ChenLin commented on KAFKA-8832:
[~guozhang] I did a test and then dumped the jvm memory
[
https://issues.apache.org/jira/browse/KAFKA-8832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16918238#comment-16918238
]
ChenLin edited comment on KAFKA-8832 at 8/29/19 3:24 AM:
-
[~guozh
[
https://issues.apache.org/jira/browse/KAFKA-8832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8832:
---
Attachment: image-2019-08-29-11-25-52-242.png
> We should limit the maximum size read by a fetch request on t
[
https://issues.apache.org/jira/browse/KAFKA-8832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-8832:
---
Description:
I found that kafka is not on the server side, limiting the amount of data read
per fetch reques
ChenLin created KAFKA-12174:
---
Summary: A program for dynamically alter log4j levels at runtime.
Key: KAFKA-12174
URL: https://issues.apache.org/jira/browse/KAFKA-12174
Project: Kafka
Issue Type: Im
ChenLin created KAFKA-17590:
---
Summary: ReplicaFetcher throw CorruptRecordException
Key: KAFKA-17590
URL: https://issues.apache.org/jira/browse/KAFKA-17590
Project: Kafka
Issue Type: Bug
C
[
https://issues.apache.org/jira/browse/KAFKA-17590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17883863#comment-17883863
]
ChenLin commented on KAFKA-17590:
-
I parsed the data of the corresponding segment file o
[
https://issues.apache.org/jira/browse/KAFKA-17590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ChenLin updated KAFKA-17590:
Priority: Blocker (was: Major)
> ReplicaFetcher throw CorruptRecordException
> --
[
https://issues.apache.org/jira/browse/KAFKA-17590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17883876#comment-17883876
]
ChenLin commented on KAFKA-17590:
-
hi [~junrao] hi [~ijuma],
could you please have a l
[
https://issues.apache.org/jira/browse/KAFKA-17590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17884078#comment-17884078
]
ChenLin commented on KAFKA-17590:
-
# SSL authentication is not enabled on the Kafka serv
[
https://issues.apache.org/jira/browse/KAFKA-17590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17884078#comment-17884078
]
ChenLin edited comment on KAFKA-17590 at 9/24/24 2:05 AM:
--
# SS
75 matches
Mail list logo
