[jira] [Commented] (KAFKA-6165) Kafka Brokers goes down with outOfMemoryError.

[ https://issues.apache.org/jira/browse/KAFKA-6165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237189#comment-16237189 ] kaushik srinivas commented on KAFKA-6165: - java version "1.8.0_112" Java(TM) SE Ru

[jira] [Commented] (KAFKA-6165) Kafka Brokers goes down with outOfMemoryError.

[ https://issues.apache.org/jira/browse/KAFKA-6165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237205#comment-16237205 ] huxihx commented on KAFKA-6165: --- Could you try to decrease the heap size a little bit? 16GB

[jira] [Commented] (KAFKA-3049) VerifiableProperties does not respect 'default' properties of underlying java.util.Properties instance

[ https://issues.apache.org/jira/browse/KAFKA-3049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237209#comment-16237209 ] Jeffrey Olchovy commented on KAFKA-3049: Saw this was updated. I believe the exist

[jira] [Commented] (KAFKA-6110) Warning when running the broker on Windows

[ https://issues.apache.org/jira/browse/KAFKA-6110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237236#comment-16237236 ] huxihx commented on KAFKA-6110: --- Seems it's a duplicate of [KAFKA-6156|https://issues.apach

[jira] [Commented] (KAFKA-6165) Kafka Brokers goes down with outOfMemoryError.

[ https://issues.apache.org/jira/browse/KAFKA-6165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237358#comment-16237358 ] kaushik srinivas commented on KAFKA-6165: - Sure will try to reduce the heap size t

[jira] [Commented] (KAFKA-6060) Add workload generation capabilities to Trogdor

[ https://issues.apache.org/jira/browse/KAFKA-6060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237359#comment-16237359 ] ASF GitHub Bot commented on KAFKA-6060: --- Github user asfgit closed the pull request

[jira] [Resolved] (KAFKA-6060) Add workload generation capabilities to Trogdor

[ https://issues.apache.org/jira/browse/KAFKA-6060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-6060. --- Resolution: Fixed Fix Version/s: 1.1.0 Issue resolved by pull request 4073 https://gith

[jira] [Created] (KAFKA-6166) Streams configuration requires consumer. and producer. in order to be read

Justin Manchester created KAFKA-6166: Summary: Streams configuration requires consumer. and producer. in order to be read Key: KAFKA-6166 URL: https://issues.apache.org/jira/browse/KAFKA-6166 Proj

[jira] [Commented] (KAFKA-6165) Kafka Brokers goes down with outOfMemoryError.

[ https://issues.apache.org/jira/browse/KAFKA-6165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237555#comment-16237555 ] kaushik srinivas commented on KAFKA-6165: - Tried with 12GB of Heap space. Observed

[jira] [Commented] (KAFKA-6165) Kafka Brokers goes down with outOfMemoryError.

[ https://issues.apache.org/jira/browse/KAFKA-6165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237563#comment-16237563 ] Ismael Juma commented on KAFKA-6165: The memory map is failing. Maybe you're running i

[jira] [Commented] (KAFKA-6165) Kafka Brokers goes down with outOfMemoryError.

[ https://issues.apache.org/jira/browse/KAFKA-6165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237567#comment-16237567 ] kaushik srinivas commented on KAFKA-6165: - Update for my previous comment, Once t

[jira] [Resolved] (KAFKA-6159) Link to upgrade docs in 1.0.0 release notes is broken

[ https://issues.apache.org/jira/browse/KAFKA-6159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-6159. -- Resolution: Fixed > Link to upgrade docs in 1.0.0 release notes is broken >

[jira] [Commented] (KAFKA-6161) Introduce new serdes interfaces with empty configure() and close()

[ https://issues.apache.org/jira/browse/KAFKA-6161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237785#comment-16237785 ] ASF GitHub Bot commented on KAFKA-6161: --- GitHub user evis opened a pull request:

[jira] [Created] (KAFKA-6167) Timestamp on streams directory contains a colon, which is an illegal character

Justin Manchester created KAFKA-6167: Summary: Timestamp on streams directory contains a colon, which is an illegal character Key: KAFKA-6167 URL: https://issues.apache.org/jira/browse/KAFKA-6167

[jira] [Commented] (KAFKA-6166) Streams configuration requires consumer. and producer. in order to be read

[ https://issues.apache.org/jira/browse/KAFKA-6166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237846#comment-16237846 ] Ted Yu commented on KAFKA-6166: --- How about populating the first two configs with the value f

[jira] [Commented] (KAFKA-6167) Timestamp on streams directory contains a colon, which is an illegal character

[ https://issues.apache.org/jira/browse/KAFKA-6167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237856#comment-16237856 ] Ted Yu commented on KAFKA-6167: --- Any suggestion for a replacement ? Semicolon ? > Timestamp

[jira] [Commented] (KAFKA-6167) Timestamp on streams directory contains a colon, which is an illegal character

[ https://issues.apache.org/jira/browse/KAFKA-6167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237875#comment-16237875 ] Adrian McCague commented on KAFKA-6167: --- `.` feels quite standard here > Timestamp

[jira] [Comment Edited] (KAFKA-6167) Timestamp on streams directory contains a colon, which is an illegal character

[ https://issues.apache.org/jira/browse/KAFKA-6167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237875#comment-16237875 ] Adrian McCague edited comment on KAFKA-6167 at 11/3/17 4:39 PM:

[jira] [Commented] (KAFKA-6164) ClientQuotaManager threads prevent shutdown when encountering an error loading logs

[ https://issues.apache.org/jira/browse/KAFKA-6164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237977#comment-16237977 ] Xavier Léauté commented on KAFKA-6164: -- [~ted_yu] that's certainly an option assuming

[jira] [Commented] (KAFKA-6163) Broker should fail fast on startup if an error occurs while loading logs

[ https://issues.apache.org/jira/browse/KAFKA-6163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237984#comment-16237984 ] Xavier Léauté commented on KAFKA-6163: -- [~ijuma] in this case it was a different fata

[jira] [Commented] (KAFKA-4682) Committed offsets should not be deleted if a consumer is still active (KIP-211)

[ https://issues.apache.org/jira/browse/KAFKA-4682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238126#comment-16238126 ] Drew Kutcharian commented on KAFKA-4682: This just happened to us and I just stumb

[jira] [Created] (KAFKA-6168) Connect Schema comparison is slow for large schemas

Randall Hauch created KAFKA-6168: Summary: Connect Schema comparison is slow for large schemas Key: KAFKA-6168 URL: https://issues.apache.org/jira/browse/KAFKA-6168 Project: Kafka Issue Type:

[jira] [Created] (KAFKA-6169) Kafka Log should reject negative timestamps

Ryan P created KAFKA-6169: - Summary: Kafka Log should reject negative timestamps Key: KAFKA-6169 URL: https://issues.apache.org/jira/browse/KAFKA-6169 Project: Kafka Issue Type: Bug Repo

[jira] [Commented] (KAFKA-6166) Streams configuration requires consumer. and producer. in order to be read

[ https://issues.apache.org/jira/browse/KAFKA-6166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238531#comment-16238531 ] Guozhang Wang commented on KAFKA-6166: -- [~wushujames] asked about this issue as well,

[jira] [Commented] (KAFKA-6168) Connect Schema comparison is slow for large schemas

[ https://issues.apache.org/jira/browse/KAFKA-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238561#comment-16238561 ] Ted Yu commented on KAFKA-6168: --- Can I work on this ? > Connect Schema comparison is slow f

[jira] [Updated] (KAFKA-6148) ClassCastException in BigQuery connector

[ https://issues.apache.org/jira/browse/KAFKA-6148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-6148: - Summary: ClassCastException in BigQuery connector (was: ERROR Commit of WorkerSin

[jira] [Updated] (KAFKA-6168) Connect Schema comparison is slow for large schemas

[ https://issues.apache.org/jira/browse/KAFKA-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated KAFKA-6168: -- Attachment: 6168.v1.txt > Connect Schema comparison is slow for large schemas >

[jira] [Comment Edited] (KAFKA-6168) Connect Schema comparison is slow for large schemas

[ https://issues.apache.org/jira/browse/KAFKA-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238561#comment-16238561 ] Ted Yu edited comment on KAFKA-6168 at 11/3/17 11:35 PM: - bq. cons

[jira] [Created] (KAFKA-6170) Add the AdminClient in Streams' KafkaClientSupplier

Guozhang Wang created KAFKA-6170: Summary: Add the AdminClient in Streams' KafkaClientSupplier Key: KAFKA-6170 URL: https://issues.apache.org/jira/browse/KAFKA-6170 Project: Kafka Issue Type:

[jira] [Assigned] (KAFKA-6148) ClassCastException in BigQuery connector

[ https://issues.apache.org/jira/browse/KAFKA-6148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava reassigned KAFKA-6148: Assignee: Konstantine Karantasis > ClassCastException in BigQuery connector

[jira] [Commented] (KAFKA-6148) ClassCastException in BigQuery connector

[ https://issues.apache.org/jira/browse/KAFKA-6148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238589#comment-16238589 ] Ewen Cheslack-Postava commented on KAFKA-6148: -- I think this is due to the ne

[jira] [Updated] (KAFKA-6167) Timestamp on streams directory contains a colon, which is an illegal character

[ https://issues.apache.org/jira/browse/KAFKA-6167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-6167: - Labels: user-experience (was: ) > Timestamp on streams directory contains a colon, which is an il

[jira] [Commented] (KAFKA-6148) ClassCastException in BigQuery connector

[ https://issues.apache.org/jira/browse/KAFKA-6148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238621#comment-16238621 ] Ewen Cheslack-Postava commented on KAFKA-6148: -- [~burd0047] Can you clarify w

[jira] [Commented] (KAFKA-6166) Streams configuration requires consumer. and producer. in order to be read

[ https://issues.apache.org/jira/browse/KAFKA-6166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238673#comment-16238673 ] James Cheng commented on KAFKA-6166: Thanks [~guozhang]. Just to make sure I understan

[jira] [Assigned] (KAFKA-6168) Connect Schema comparison is slow for large schemas

[ https://issues.apache.org/jira/browse/KAFKA-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch reassigned KAFKA-6168: Assignee: Ted Yu > Connect Schema comparison is slow for large schemas > --

[jira] [Commented] (KAFKA-6168) Connect Schema comparison is slow for large schemas

[ https://issues.apache.org/jira/browse/KAFKA-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238698#comment-16238698 ] Randall Hauch commented on KAFKA-6168: -- [~yuzhih...@gmail.com], thanks for offering t

[jira] [Commented] (KAFKA-6168) Connect Schema comparison is slow for large schemas

[ https://issues.apache.org/jira/browse/KAFKA-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238704#comment-16238704 ] ASF GitHub Bot commented on KAFKA-6168: --- GitHub user tedyu opened a pull request:

[jira] [Updated] (KAFKA-6074) Use ZookeeperClient in ReplicaManager and Partition

[ https://issues.apache.org/jira/browse/KAFKA-6074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated KAFKA-6074: -- Attachment: 6074.v10.txt > Use ZookeeperClient in ReplicaManager and Partition > ---

[jira] [Updated] (KAFKA-5863) Potential null dereference in DistributedHerder#reconfigureConnector()

[ https://issues.apache.org/jira/browse/KAFKA-5863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated KAFKA-5863: -- Description: Here is the call chain: {code} RestServer.httpRequest(reconfigUrl,

[jira] [Commented] (KAFKA-6161) Introduce new serdes interfaces with empty configure() and close()

[ https://issues.apache.org/jira/browse/KAFKA-6161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238790#comment-16238790 ] Kamal Chandraprakash commented on KAFKA-6161: - My opinion is that we can do th