[jira] [Commented] (KAFKA-3472) Allow MirrorMaker to copy selected partitions and choose target topic name

2016-03-26 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15213355#comment-15213355 ] ASF GitHub Bot commented on KAFKA-3472: --- GitHub user hsun-cnnxty opened a pull reque

[GitHub] kafka pull request: [KAFKA-3472] Allow MirrorMaker to copy selecte...

2016-03-26 Thread hsun-cnnxty
GitHub user hsun-cnnxty opened a pull request: https://github.com/apache/kafka/pull/1147 [KAFKA-3472] Allow MirrorMaker to copy selected partitions and choose target topic name Please see the jira issue for detail: https://issues.apache.org/jira/browse/KAFKA-3472 You can merge thi

[jira] [Updated] (KAFKA-3472) Allow MirrorMaker to copy selected partitions and choose target topic name

2016-03-26 Thread Hang Sun (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hang Sun updated KAFKA-3472: Description: It would be nice if MirrorMaker can be used to copy only a few partitions instead of all to a d

[jira] [Updated] (KAFKA-3472) Allow MirrorMaker to copy selected partitions and choose target topic name

2016-03-26 Thread Hang Sun (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hang Sun updated KAFKA-3472: Summary: Allow MirrorMaker to copy selected partitions and choose target topic name (was: Allow MirrorMaker

[jira] [Updated] (KAFKA-3472) Allow MirrorMaker to copy selected partitions

2016-03-26 Thread Hang Sun (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hang Sun updated KAFKA-3472: Flags: Patch > Allow MirrorMaker to copy selected partitions > -

[jira] [Created] (KAFKA-3472) Allow MirrorMaker to copy selected partitions

2016-03-26 Thread Hang Sun (JIRA)
Hang Sun created KAFKA-3472: --- Summary: Allow MirrorMaker to copy selected partitions Key: KAFKA-3472 URL: https://issues.apache.org/jira/browse/KAFKA-3472 Project: Kafka Issue Type: Improvement

Build failed in Jenkins: kafka-0.10.0-jdk7 #18

2016-03-26 Thread Apache Jenkins Server
See Changes: [junrao] KAFKA-3388; Fix expiration of batches sitting in the accumulator -- [...truncated 3118 lines...] kafka.log.BrokerCompressionTest > testBrokerSideCompression[17] PASSED kaf

[jira] [Updated] (KAFKA-3471) min.insync.replicas isn't respected when there's a delaying follower who still in ISR

2016-03-26 Thread Yuto Kawamura (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuto Kawamura updated KAFKA-3471: - Status: Patch Available (was: Open) > min.insync.replicas isn't respected when there's a delaying

[jira] [Commented] (KAFKA-3471) min.insync.replicas isn't respected when there's a delaying follower who still in ISR

2016-03-26 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15213133#comment-15213133 ] ASF GitHub Bot commented on KAFKA-3471: --- GitHub user kawamuray opened a pull request

[GitHub] kafka pull request: KAFKA-3471: min.insync.replicas isn't respecte...

2016-03-26 Thread kawamuray
GitHub user kawamuray opened a pull request: https://github.com/apache/kafka/pull/1146 KAFKA-3471: min.insync.replicas isn't respected when there's a delaying follower who still in ISR Ticket: https://issues.apache.org/jira/browse/KAFKA-3471 The number of followers which ar

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

2016-03-26 Thread Apache Jenkins Server
See Changes: [junrao] KAFKA-3388; Fix expiration of batches sitting in the accumulator -- [...truncated 1594 lines...] kafka.log.LogTest > testTruncateTo PASSED kafka.log.LogTest > testCleanSh

[jira] [Updated] (KAFKA-3471) min.insync.replicas isn't respected when there's a delaying follower who still in ISR

2016-03-26 Thread Yuto Kawamura (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuto Kawamura updated KAFKA-3471: - Description: tl;dr; Partition.checkEnoughReplicasReachOffset should see the number of followers

[jira] [Updated] (KAFKA-3471) min.insync.replicas isn't respected when there's a delaying follower who still in ISR

2016-03-26 Thread Yuto Kawamura (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuto Kawamura updated KAFKA-3471: - Description: h2. tl;dr; Partition.checkEnoughReplicasReachOffset should see the number of follower

[jira] [Created] (KAFKA-3471) min.insync.replicas isn't respected when there's a delaying follower who still in ISR

2016-03-26 Thread Yuto Kawamura (JIRA)
Yuto Kawamura created KAFKA-3471: Summary: min.insync.replicas isn't respected when there's a delaying follower who still in ISR Key: KAFKA-3471 URL: https://issues.apache.org/jira/browse/KAFKA-3471 P

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

2016-03-26 Thread Apache Jenkins Server
See Changes: [junrao] KAFKA-3388; Fix expiration of batches sitting in the accumulator -- [...truncated 838 lines...] kafka.server.IsrExpirationTest > testIsrExpirationForSlowFollowers PASSED ka

[jira] [Commented] (KAFKA-3388) Producer should only timeout a batch in the accumulator when metadata is missing.

2016-03-26 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15213096#comment-15213096 ] ASF GitHub Bot commented on KAFKA-3388: --- Github user asfgit closed the pull request

[jira] [Updated] (KAFKA-3388) Producer should only timeout a batch in the accumulator when metadata is missing.

2016-03-26 Thread Jun Rao (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-3388: --- Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request 1056 [https:

[GitHub] kafka pull request: KAFKA-3388: Fix expiration of batches sitting ...

2016-03-26 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1056 --- 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-3456) In-house KafkaMetric misreports metrics when periodically observed

2016-03-26 Thread The Data Lorax (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15213062#comment-15213062 ] The Data Lorax commented on KAFKA-3456: --- Yep, increasing the number of samples certa

[GitHub] kafka pull request: [MINOR] server stop scripts don't work correct...

2016-03-26 Thread sasakitoa
GitHub user sasakitoa opened a pull request: https://github.com/apache/kafka/pull/1145 [MINOR] server stop scripts don't work correctlly in shell kafka-server-stop.sh and zookeeper-server-stop.sh don't work in shell. (however these work correctlly in bash) You can merge th

[jira] [Resolved] (KAFKA-2954) reserved.broker.max.id is not fully documented

2016-03-26 Thread Andrea Cosentino (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-2954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved KAFKA-2954. - Resolution: Fixed > reserved.broker.max.id is not fully documented > -

[jira] [Assigned] (KAFKA-2954) reserved.broker.max.id is not fully documented

2016-03-26 Thread Andrea Cosentino (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-2954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned KAFKA-2954: --- Assignee: Andrea Cosentino > reserved.broker.max.id is not fully documented > ---

[jira] [Commented] (KAFKA-2954) reserved.broker.max.id is not fully documented

2016-03-26 Thread Andrea Cosentino (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-2954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15212971#comment-15212971 ] Andrea Cosentino commented on KAFKA-2954: - This seems to be ok in the latest docum

[jira] [Work stopped] (KAFKA-3385) Need to log "Rejected connection" as WARNING message

2016-03-26 Thread Andrea Cosentino (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-3385 stopped by Andrea Cosentino. --- > Need to log "Rejected connection" as WARNING message > --

[jira] [Commented] (KAFKA-3385) Need to log "Rejected connection" as WARNING message

2016-03-26 Thread Andrea Cosentino (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15212962#comment-15212962 ] Andrea Cosentino commented on KAFKA-3385: - PR submitted: https://github.com/apache

[GitHub] kafka pull request: KAFKA-3385: Need to log "Rejected connection" ...

2016-03-26 Thread oscerd
GitHub user oscerd opened a pull request: https://github.com/apache/kafka/pull/1144 KAFKA-3385: Need to log "Rejected connection" as WARNING message Hi all, This PR is related to: https://issues.apache.org/jira/browse/KAFKA-3385 Thanks, Andrea You can

[jira] [Commented] (KAFKA-3385) Need to log "Rejected connection" as WARNING message

2016-03-26 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15212961#comment-15212961 ] ASF GitHub Bot commented on KAFKA-3385: --- GitHub user oscerd opened a pull request:

[jira] [Work started] (KAFKA-3385) Need to log "Rejected connection" as WARNING message

2016-03-26 Thread Andrea Cosentino (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-3385 started by Andrea Cosentino. --- > Need to log "Rejected connection" as WARNING message > --

[jira] [Assigned] (KAFKA-3385) Need to log "Rejected connection" as WARNING message

2016-03-26 Thread Andrea Cosentino (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned KAFKA-3385: --- Assignee: Andrea Cosentino > Need to log "Rejected connection" as WARNING message > -

[jira] [Commented] (KAFKA-3449) Rename filterOut() to filterNot() to achieve better terminology

2016-03-26 Thread Andrea Cosentino (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-3449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15212925#comment-15212925 ] Andrea Cosentino commented on KAFKA-3449: - Thank you very much :-) > Rename filte

[jira] [Created] (KAFKA-3470) Consumer group coordinator should take commit requests as effective as heartbeats

2016-03-26 Thread Zaiming Shi (JIRA)
Zaiming Shi created KAFKA-3470: -- Summary: Consumer group coordinator should take commit requests as effective as heartbeats Key: KAFKA-3470 URL: https://issues.apache.org/jira/browse/KAFKA-3470 Project: