[jira] [Commented] (KAFKA-3230) Unable to commit offsets if partition is paused

2016-02-12 Thread Craig W (JIRA)

[ 
https://issues.apache.org/jira/browse/KAFKA-3230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15144400#comment-15144400
 ] 

Craig W commented on KAFKA-3230:


Yup, this is not a problem.

> Unable to commit offsets if partition is paused
> ---
>
> Key: KAFKA-3230
> URL: https://issues.apache.org/jira/browse/KAFKA-3230
> Project: Kafka
>  Issue Type: Bug
>  Components: clients
>Affects Versions: 0.9.0.0
>Reporter: Craig W
>
> If I pause a topic partition, then try to 
> [commitSync(java.util.Map 
> offsets)|http://kafka.apache.org/090/javadoc/org/apache/kafka/clients/consumer/KafkaConsumer.html#commitSync(java.util.Map)]
>  to that partition, no error is thrown and the offset does not actually get 
> committed.
> It seems I have to resume before being able to commit offsets. This behavior 
> is unexpected, at least based on the documentation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Resolved] (KAFKA-3230) Unable to commit offsets if partition is paused

2016-02-12 Thread Craig W (JIRA)

 [ 
https://issues.apache.org/jira/browse/KAFKA-3230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Craig W resolved KAFKA-3230.

Resolution: Not A Problem

> Unable to commit offsets if partition is paused
> ---
>
> Key: KAFKA-3230
> URL: https://issues.apache.org/jira/browse/KAFKA-3230
> Project: Kafka
>  Issue Type: Bug
>  Components: clients
>Affects Versions: 0.9.0.0
>Reporter: Craig W
>
> If I pause a topic partition, then try to 
> [commitSync(java.util.Map 
> offsets)|http://kafka.apache.org/090/javadoc/org/apache/kafka/clients/consumer/KafkaConsumer.html#commitSync(java.util.Map)]
>  to that partition, no error is thrown and the offset does not actually get 
> committed.
> It seems I have to resume before being able to commit offsets. This behavior 
> is unexpected, at least based on the documentation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (KAFKA-3230) Unable to commit offsets if partition is paused

2016-02-11 Thread Craig W (JIRA)

[ 
https://issues.apache.org/jira/browse/KAFKA-3230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15143231#comment-15143231
 ] 

Craig W commented on KAFKA-3230:


So the problem appears to be on my misunderstanding of committing offsets. If I 
got a message for topic foo, partition 0, offset 1 (aka "foo-0 1"), I would do 
whatever processing I needed for that message and then I would call commitSync 
with "foo-0 1". However, it seems I should've committed "foo-0 2"!  When 
committing an offset that's +1 over what I processed, it works as expected.

Am I correct that when committing offsets you need to commit an offset number 
that's +1 over the message that was processed? Meaning:

get message from "foo", gets back "foo-0 1"
do work
commitSync("foo-0 2")

> Unable to commit offsets if partition is paused
> ---
>
> Key: KAFKA-3230
> URL: https://issues.apache.org/jira/browse/KAFKA-3230
> Project: Kafka
>  Issue Type: Bug
>  Components: clients
>Affects Versions: 0.9.0.0
>Reporter: Craig W
>
> If I pause a topic partition, then try to 
> [commitSync(java.util.Map 
> offsets)|http://kafka.apache.org/090/javadoc/org/apache/kafka/clients/consumer/KafkaConsumer.html#commitSync(java.util.Map)]
>  to that partition, no error is thrown and the offset does not actually get 
> committed.
> It seems I have to resume before being able to commit offsets. This behavior 
> is unexpected, at least based on the documentation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Created] (KAFKA-3230) Unable to commit offsets if partition is paused

2016-02-11 Thread Craig W (JIRA)
Craig W created KAFKA-3230:
--

 Summary: Unable to commit offsets if partition is paused
 Key: KAFKA-3230
 URL: https://issues.apache.org/jira/browse/KAFKA-3230
 Project: Kafka
  Issue Type: Bug
  Components: clients
Affects Versions: 0.9.0.0
Reporter: Craig W


If I pause a topic partition, then try to 
[commitSync(java.util.Map 
offsets)|http://kafka.apache.org/090/javadoc/org/apache/kafka/clients/consumer/KafkaConsumer.html#commitSync(java.util.Map)]
 to that partition, no error is thrown and the offset does not actually get 
committed.

It seems I have to resume before being able to commit offsets. This behavior is 
unexpected, at least based on the documentation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Created] (KAFKA-2751) Documentation for retention.ms is confusing

2015-11-05 Thread Craig W (JIRA)
Craig W created KAFKA-2751:
--

 Summary: Documentation for retention.ms is confusing
 Key: KAFKA-2751
 URL: https://issues.apache.org/jira/browse/KAFKA-2751
 Project: Kafka
  Issue Type: Bug
Affects Versions: 0.8.2.1
Reporter: Craig W
Priority: Minor


The documentation for the "retention.ms" setting is a little confusing. When 
looking at the documentation the property is in the first column, while the 
default server property is in the 3rd column which is named 
"log.retention.minutes". The description for the property doesn't describe the 
expected value, so it leads one to believe maybe "retention.ms" is meant to be 
minutes.

I'd like to see the description for the property explicitly mention that the 
value at the topic level is milliseconds, where as it's minutes for the server 
level.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)