[jira] [Issue Comment Deleted] (KAFKA-6898) org.apache.kafka.common.errors.TimeoutException
[
https://issues.apache.org/jira/browse/KAFKA-6898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doron Levi updated KAFKA-6898:
--
Comment: was deleted
(was: I think there is a bug in class BufferPool, nonPooledAvailableMemory
seems to never go up, even when memory is freed, when you
return this.free.pollFirst() you should add back memory to
nonPooledAvailableMemory (free memory should "live" either in this.free queue
or in nonPooledAvailableMemory)
)
> org.apache.kafka.common.errors.TimeoutException
> ---
>
> Key: KAFKA-6898
> URL: https://issues.apache.org/jira/browse/KAFKA-6898
> Project: Kafka
> Issue Type: Bug
> Components: producer
>Affects Versions: 0.10.2.0
> Environment: Production
>Reporter: Rishi
>Priority: Major
>
> Getting error
> {code:java}
> org.apache.kafka.common.errors.TimeoutException Failed to allocate memory
> within the configured max blocking time 59927 ms.{code}
> while publishing events to Kafka. We are using Kafka Java client 0.10.2.0
> with Kafka 0.10.1.0 broker.
> This issue does not happen always but after certain time of applications
> running in service, it starts happening and applications never recover from
> this state until the producer instance is restarted.
> The configuration of producer and on Kafka broker is default and hasn't been
> changed. What should be the course of action for this issue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (KAFKA-13285) Use consistent access modifier for Admin clients Result classes
[ https://issues.apache.org/jira/browse/KAFKA-13285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17413733#comment-17413733 ] Tom Bentley commented on KAFKA-13285: - [~vijaykriishna] I opened [KIP-774|https://cwiki.apache.org/confluence/display/KAFKA/KIP-774%3A+Deprecate+public+access+to+Admin+client%27s+*Result+constructors] about this last week. That will need to be approved before any PR for this issue can be merged. > Use consistent access modifier for Admin clients Result classes > --- > > Key: KAFKA-13285 > URL: https://issues.apache.org/jira/browse/KAFKA-13285 > Project: Kafka > Issue Type: Task > Components: admin >Affects Versions: 3.0.0 >Reporter: Tom Bentley >Assignee: Vijay >Priority: Minor > > The following classes in the Admin client have public constructors, while the > rest have package-private constructors: > AlterClientQuotasResult > AlterUserScramCredentialsResult > DeleteRecordsResult > DescribeClientQuotasResult > DescribeConsumerGroupsResult > ListOffsetsResult > There should be consistency across all the Result classes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (KAFKA-6898) org.apache.kafka.common.errors.TimeoutException
[
https://issues.apache.org/jira/browse/KAFKA-6898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17413710#comment-17413710
]
Doron Levi commented on KAFKA-6898:
---
I think there is a bug in class BufferPool, nonPooledAvailableMemory seems to
never go up, even when memory is freed, when you
return this.free.pollFirst() you should add back memory to
nonPooledAvailableMemory (free memory should "live" either in this.free queue
or in nonPooledAvailableMemory)
> org.apache.kafka.common.errors.TimeoutException
> ---
>
> Key: KAFKA-6898
> URL: https://issues.apache.org/jira/browse/KAFKA-6898
> Project: Kafka
> Issue Type: Bug
> Components: producer
>Affects Versions: 0.10.2.0
> Environment: Production
>Reporter: Rishi
>Priority: Major
>
> Getting error
> {code:java}
> org.apache.kafka.common.errors.TimeoutException Failed to allocate memory
> within the configured max blocking time 59927 ms.{code}
> while publishing events to Kafka. We are using Kafka Java client 0.10.2.0
> with Kafka 0.10.1.0 broker.
> This issue does not happen always but after certain time of applications
> running in service, it starts happening and applications never recover from
> this state until the producer instance is restarted.
> The configuration of producer and on Kafka broker is default and hasn't been
> changed. What should be the course of action for this issue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (KAFKA-7360) Code example in "Accessing Processor Context" misses a closing parenthesis
[
https://issues.apache.org/jira/browse/KAFKA-7360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vijay reassigned KAFKA-7360:
Assignee: Vijay
> Code example in "Accessing Processor Context" misses a closing parenthesis
> --
>
> Key: KAFKA-7360
> URL: https://issues.apache.org/jira/browse/KAFKA-7360
> Project: Kafka
> Issue Type: Bug
> Components: documentation
>Affects Versions: 2.0.0
>Reporter: Sven Erik Knop
>Assignee: Vijay
>Priority: Minor
>
> https://kafka.apache.org/20/documentation/streams/developer-guide/processor-api.html#accessing-processor-context
> Code example has some issues:
> public void process(String key, String value) {
>
> // add a header to the elements
> context().headers().add.("key", "key"
> }
> Should be
> public void process(String key, String value) {
>
> // add a header to the elements
> context().headers().add("key", "value")
> }
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (KAFKA-7360) Code example in "Accessing Processor Context" misses a closing parenthesis
[
https://issues.apache.org/jira/browse/KAFKA-7360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17413701#comment-17413701
]
Vijay commented on KAFKA-7360:
--
Please review [https://github.com/apache/kafka/pull/10873]
> Code example in "Accessing Processor Context" misses a closing parenthesis
> --
>
> Key: KAFKA-7360
> URL: https://issues.apache.org/jira/browse/KAFKA-7360
> Project: Kafka
> Issue Type: Bug
> Components: documentation
>Affects Versions: 2.0.0
>Reporter: Sven Erik Knop
>Assignee: Vijay
>Priority: Minor
>
> https://kafka.apache.org/20/documentation/streams/developer-guide/processor-api.html#accessing-processor-context
> Code example has some issues:
> public void process(String key, String value) {
>
> // add a header to the elements
> context().headers().add.("key", "key"
> }
> Should be
> public void process(String key, String value) {
>
> // add a header to the elements
> context().headers().add("key", "value")
> }
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (KAFKA-13285) Use consistent access modifier for Admin clients Result classes
[ https://issues.apache.org/jira/browse/KAFKA-13285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vijay reassigned KAFKA-13285: - Assignee: Vijay > Use consistent access modifier for Admin clients Result classes > --- > > Key: KAFKA-13285 > URL: https://issues.apache.org/jira/browse/KAFKA-13285 > Project: Kafka > Issue Type: Task > Components: admin >Affects Versions: 3.0.0 >Reporter: Tom Bentley >Assignee: Vijay >Priority: Minor > > The following classes in the Admin client have public constructors, while the > rest have package-private constructors: > AlterClientQuotasResult > AlterUserScramCredentialsResult > DeleteRecordsResult > DescribeClientQuotasResult > DescribeConsumerGroupsResult > ListOffsetsResult > There should be consistency across all the Result classes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (KAFKA-6898) org.apache.kafka.common.errors.TimeoutException
[
https://issues.apache.org/jira/browse/KAFKA-6898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17413664#comment-17413664
]
Doron Levi commented on KAFKA-6898:
---
This happens to me as well... any updates? I am using the same producer in
multiple threads, is it related?
> org.apache.kafka.common.errors.TimeoutException
> ---
>
> Key: KAFKA-6898
> URL: https://issues.apache.org/jira/browse/KAFKA-6898
> Project: Kafka
> Issue Type: Bug
> Components: producer
>Affects Versions: 0.10.2.0
> Environment: Production
>Reporter: Rishi
>Priority: Major
>
> Getting error
> {code:java}
> org.apache.kafka.common.errors.TimeoutException Failed to allocate memory
> within the configured max blocking time 59927 ms.{code}
> while publishing events to Kafka. We are using Kafka Java client 0.10.2.0
> with Kafka 0.10.1.0 broker.
> This issue does not happen always but after certain time of applications
> running in service, it starts happening and applications never recover from
> this state until the producer instance is restarted.
> The configuration of producer and on Kafka broker is default and hasn't been
> changed. What should be the course of action for this issue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
