Re: Queryable state client read guarantees

Hi, this helps, thanks! Basically, after each read, I'll check if the key is still supposed to be on the host. Doing the check after the read is necessary to handle the case when a rebalance happens in between the metadata lookup and the store get. When checking after the read, it may happen that

Build failed in Jenkins: kafka-trunk-jdk8 #877

See Changes: [wangguoz] MINOR: catch InvalidStateStoreException in QueryableStateIntegrationTest -- [...truncated 12374 lines...] org.apache.kafka.streams.kstream.KStreamBuilderTest > testMerge

[GitHub] kafka pull request #1840: MINOR: catch InvalidStateStoreException in Queryab...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1840 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

Re: Queryable state client read guarantees

Hi Mikael, Just adding to Damian's comment above, that the IllegalStateStoreException here is thrown to indicate a "transient" state where the state store hosting this key is being migrated and hence not available, where users implementing the REST APIs on top of it, for example, can choose to han

Build failed in Jenkins: kafka-trunk-jdk7 #1533

See Changes: [junrao] KAFKA-1981; Make log compaction point configurable -- [...truncated 1073 lines...] kafka.server.SaslPlaintextReplicaFetchTest > testReplicaFetcherThread STARTED kafka.serv

[jira] [Resolved] (KAFKA-1981) Make log compaction point configurable

[ https://issues.apache.org/jira/browse/KAFKA-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-1981. Resolution: Fixed Fix Version/s: 0.10.1.0 Issue resolved by pull request 1794 [https://github.com/apa

[GitHub] kafka pull request #1794: KAFKA-1981 Make log compaction point configurable

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1794 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

[jira] [Commented] (KAFKA-1981) Make log compaction point configurable

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

Re: [DISCUSS] KIP-72 Allow Sizing Incoming Request Queue in Bytes

Hi, Radai, Thanks for the reply. I still have a followup question on #2. My understanding is that in your proposal, selector will now first read the size of the Receive. If there is not enough memory, it has to turn off the READ interest bit for the corresponding KafkaChannel. Otherwise, subseque

Re: [DISCUSS] Kafka 0.10.1.0 Release Plan

Hey Rajini, We took a long look at KIP-55 and decided that the time needed to review, stabilize, and add system testing might not be sufficient. Usually a somewhat large patch like that takes a couple weeks of iteration before landing in trunk. For a new security feature, it might be even longer.

Build failed in Jenkins: kafka-trunk-jdk7 #1532

See Changes: [ismael] KAFKA-4147; Fix transient failure in -- [...truncated 12295 lines...] org.apache.kafka.streams.processor.internals.StreamTaskTest > testMaybePunctuate PASSED org.apache.k

Jenkins build is back to normal : kafka-trunk-jdk8 #875

See

[jira] [Resolved] (KAFKA-4147) Transient failure in ConsumerCoordinatorTest.testAutoCommitDynamicAssignment

[ https://issues.apache.org/jira/browse/KAFKA-4147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-4147. Resolution: Fixed Reviewer: Ismael Juma > Transient failure in ConsumerCoordinatorTest.testAut

[jira] [Updated] (KAFKA-4147) Transient failure in ConsumerCoordinatorTest.testAutoCommitDynamicAssignment

[ https://issues.apache.org/jira/browse/KAFKA-4147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4147: --- Fix Version/s: 0.10.1.0 > Transient failure in ConsumerCoordinatorTest.testAutoCommitDynamicAssignment

[GitHub] kafka pull request #1841: KAFKA-4147: Fix transient failure in ConsumerCoord...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1841 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

[jira] [Commented] (KAFKA-4147) Transient failure in ConsumerCoordinatorTest.testAutoCommitDynamicAssignment

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

[jira] [Commented] (KAFKA-4130) [docs] Link to Varnish architect notes is broken

[ https://issues.apache.org/jira/browse/KAFKA-4130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15481236#comment-15481236 ] Andrea Cosentino commented on KAFKA-4130: - PR submitted: https://github.com/apach