[GitHub] kafka pull request #4306: KAFKA-6331; Fix transient failure in AdminClientIn...

2017-12-08 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/4306

KAFKA-6331; Fix transient failure in 
AdminClientIntegrationTest.testAlterReplicaLogDirs

*More detailed description of your change,
if necessary. The PR title and PR message become
the squashed commit message, so use a separate
comment to ping reviewers.*

*Summary of testing strategy (including rationale)
for the feature or bug fix. Unit and/or integration
tests are expected for any behaviour change and
system tests should be considered for larger changes.*

### Committer Checklist (excluded from commit message)
- [ ] Verify design and implementation 
- [ ] Verify test coverage and CI build status
- [ ] Verify documentation (including upgrade notes)


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-6331

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/4306.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #4306


commit f5c364e774a7a3b75fc49f8f5eb6bb707d1e799d
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-12-08T18:34:16Z

KAFKA-6331; Fix transient failure in 
AdminClientIntegrationTest.testAlterReplicaLogDirs




---


[GitHub] kafka pull request #4257: KAFKA-6174; Add methods in Options classes to keep...

2017-11-22 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/4257

KAFKA-6174; Add methods in Options classes to keep binary compatibility 
with 0.11

From 0.11 to 1.0, we moved `DescribeClusterOptions timeoutMs(Integer 
timeoutMs)` from DescribeClusterOptions to AbstractOptions. User reports that 
code compiled against 0.11.0 fails when it is executed with 1.0 kafka-clients 
jar. This patch adds back these methods to keep binary compatibility with 0.11.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-6174

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/4257.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #4257


commit be3069d99e1da91d7bb2aa00be1c4e0b2050ad39
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-11-23T01:14:02Z

KAFKA-6174; Add methods in Options classes to keep binary compatibility 
with 0.11




---


[GitHub] kafka pull request #4248: KAFKA-6258; SSLTransportLayer should keep reading ...

2017-11-21 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/4248

KAFKA-6258; SSLTransportLayer should keep reading from socket until either 
the buffer is full or the socket has no more data



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-6258

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/4248.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #4248


commit 12907b1a13a34f1b71c073b0a662e4c23eba20c0
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-11-22T04:08:50Z

KAFKA-6258; SSLTransportLayer should keep reading from socket until either 
the buffer is full or the socket has no more data




---


[GitHub] kafka pull request #4179: KAFKA-6175; AbstractIndex should cache index file ...

2017-11-05 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/4179

KAFKA-6175; AbstractIndex should cache index file to avoid unnecessary disk 
access during resize()



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-6175

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/4179.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #4179


commit c260ee2e7973bc4c9f3ec36d2215fc069b7619dc
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-11-05T21:40:21Z

KAFKA-6175; AbstractIndex should cache index file to avoid unnecessary disk 
access during resize()




---


[GitHub] kafka pull request #4177: KAFKA-6172; Cache lastEntry in TimeIndex to avoid ...

2017-11-05 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/4177

KAFKA-6172; Cache lastEntry in TimeIndex to avoid unnecessary disk access



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-6172

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/4177.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #4177


commit 6a413ce9f233c3554450e006da885e8435e56502
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-11-05T07:20:35Z

KAFKA-6172; Cache lastEntry in TimeIndex to avoid unnecessary disk access




---


[GitHub] kafka pull request #4100: KAFKA-6093; log.close() should not prevent log fro...

2017-10-20 Thread lindong28
Github user lindong28 closed the pull request at:

https://github.com/apache/kafka/pull/4100


---


[GitHub] kafka pull request #4100: KAFKA-6093; log.close() should not prevent log fro...

2017-10-19 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/4100

KAFKA-6093; log.close() should not prevent log from being accessed



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-6093

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/4100.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #4100


commit 3cba61a5c52e06c9841064c68dcbe1fd459dea5b
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-10-20T02:39:06Z

KAFKA-6093; log.close() should not prevent log from being accessed




---


[GitHub] kafka pull request #3782: KAFKA-5829; Speedup broker startup after unclean s...

2017-10-17 Thread lindong28
Github user lindong28 closed the pull request at:

https://github.com/apache/kafka/pull/3782


---


[GitHub] kafka pull request #3839: KAFKA-5877; Controller should only update reassign...

2017-10-05 Thread lindong28
Github user lindong28 closed the pull request at:

https://github.com/apache/kafka/pull/3839


---


[GitHub] kafka pull request #3993: KAFKA-5995; Rename AlterReplicaDir to AlterReplica...

2017-09-29 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/3993

KAFKA-5995; Rename AlterReplicaDir to AlterReplicaDirs



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-5995

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/3993.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3993


commit 9f2fe98aa0c611d65fb876c24a3738b3738c7287
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-09-29T15:21:14Z

KAFKA-5995; Rename AlterReplicaDir to AlterReplicaDirs




---


[GitHub] kafka pull request #3874: KAFKA-5163; Support replicas movement between log ...

2017-09-15 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/3874

KAFKA-5163; Support replicas movement between log directories (KIP-113)



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-5163

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/3874.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3874


commit d85e65be124aaf30eb39d90906197639be0da128
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-09-14T01:30:33Z

KAFKA-5163; Support replicas movement between log directories (KIP-113)




---


[GitHub] kafka pull request #3840: KAFKA-5879; Controller should read the latest IsrC...

2017-09-12 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/3840

KAFKA-5879; Controller should read the latest IsrChangeNotification znodes 
when handling IsrChangeNotification event

…

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-5879

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/3840.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3840


commit 54160a4d1780e58317e14f75754b40cefb5ac79a
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-09-12T22:38:26Z

KAFKA-5879; Controller should read the latest IsrChangeNotification znodes 
when handling IsrChangeNotification event




---


[GitHub] kafka pull request #3839: KAFKA-5877; Controller should only update reassign...

2017-09-12 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/3839

KAFKA-5877; Controller should only update reassignment znode if there is 
change in the reassignment data



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-5877

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/3839.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3839


commit 4cd104b6f30d4a0203816d4daa2141b60461cc93
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-09-12T21:24:54Z

KAFKA-5877; Controller should only update reassignment znode if there is 
change in the reassignment data




---


[GitHub] kafka pull request #3803: KAFKA-5845; KafkaController should send LeaderAndI...

2017-09-11 Thread lindong28
Github user lindong28 closed the pull request at:

https://github.com/apache/kafka/pull/3803


---


[GitHub] kafka pull request #3803: KAFKA-5845; KafkaController should send LeaderAndI...

2017-09-10 Thread lindong28
GitHub user lindong28 reopened a pull request:

https://github.com/apache/kafka/pull/3803

KAFKA-5845; KafkaController should send LeaderAndIsrRequest to broker which 
starts very soon after shutdown



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-5845

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/3803.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3803


commit 81b54d07d7b0eb3547bc57dbc133d9dbc793756b
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-08-27T23:58:08Z

KAFKA-5845; KafkaController should send LeaderAndIsrRequest to broker which 
starts very soon after shutdown




---


[GitHub] kafka pull request #3803: KAFKA-5845; KafkaController should send LeaderAndI...

2017-09-08 Thread lindong28
Github user lindong28 closed the pull request at:

https://github.com/apache/kafka/pull/3803


---


[GitHub] kafka pull request #3820: KAFKA-5864; ReplicaFetcherThread.processPartitionD...

2017-09-08 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/3820

KAFKA-5864; ReplicaFetcherThread.processPartitionData() should throw 
KafkaStorageException if replica is offline



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-5864

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/3820.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3820


commit 85dd401508b4706c88c7277e9c6c105e1fd5cdb4
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-09-08T21:26:24Z

KAFKA-5864; ReplicaFetcherThread.processPartitionData() should throw 
KafkaStorageException if replica is offline




---


[GitHub] kafka pull request #3803: KAFKA-5845; KafkaController should send LeaderAndI...

2017-09-06 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/3803

KAFKA-5845; KafkaController should send LeaderAndIsrRequest to broker which 
starts very soon after shutdown



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-5845

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/3803.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3803


commit 58e8100769610cad883e73cb38302ae76b48d66d
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-08-27T23:58:08Z

KAFKA-5845; KafkaController should send LeaderAndIsrRequest to brokers 
which starts very soon after shutdown




---


[GitHub] kafka pull request #3797: KAFKA-5843; Mx4jLoader.maybeLoad should only be ex...

2017-09-05 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/3797

KAFKA-5843; Mx4jLoader.maybeLoad should only be executed if 
kafka_mx4jenable is set to true



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-5843

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/3797.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3797


commit 5c1bd1c09d975dfde7f1831bf5cd091b4440bfa1
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-09-06T05:11:46Z

KAFKA-5843; Mx4jLoader.maybeLoad should only be executed if 
kafka_mx4jenable is set to true




---


[GitHub] kafka pull request #3782: KAFKA-5829; Speedup broker startup after unclean s...

2017-09-04 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/3782

KAFKA-5829; Speedup broker startup after unclean shutdown by reducing 
unnecessary snapshot files deletion



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-5829

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/3782.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3782


commit b7f08944d9f7053489498636f64762728a9b50d6
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-09-04T08:26:23Z

KAFKA-5829; Speedup broker startup after unclean shutdown by reducing 
unnecessary snapshot files deletion




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request #3781: MINOR: Improve documentation of AdminClient

2017-09-03 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/3781

MINOR: Improve documentation of AdminClient



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka minor-admin-client-comment

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/3781.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3781


commit c79a6bc087762b85518b174e017349c9798c3505
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-09-03T19:09:43Z

MINOR: Improve documentation of AdminClient




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request #3763: KAFKA-5812; Represent logDir with case class where...

2017-08-30 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/3763

KAFKA-5812; Represent logDir with case class where absolute path is required



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-5812

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/3763.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3763


commit f0dec0b5ee61ba8269c6ccf5f23be44adc31d3af
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-08-30T21:53:15Z

KAFKA-5812; Represent logDir with case class where absolute path is required




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request #3718: KAFKA-5767; Kafka server should halt if IBP < 1.0....

2017-08-22 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/3718

KAFKA-5767; Kafka server should halt if IBP < 1.0.0 and there is log 
directory failure



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-5767

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/3718.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3718


commit e3ca5fa9b5d78b987652bb2d1b7600e2df992109
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-08-22T23:40:17Z

KAFKA-5767; Kafka server should halt if IBP < 1.0.0 and there is log 
directory failure




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request #3709: KAFKA-5759; Allow user to specify relative path as...

2017-08-21 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/3709

KAFKA-5759; Allow user to specify relative path as log directory



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-5759

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/3709.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3709


commit 18a021ed46a7c8a9544c84ebdacc9dde97a90673
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-08-21T22:01:27Z

KAFKA-5759; Allow user to specify relative path as log directory




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request #3642: KafkaAdminClient should remove inflight call corre...

2017-08-08 Thread lindong28
Github user lindong28 closed the pull request at:

https://github.com/apache/kafka/pull/3642


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request #3642: KafkaAdminClient should remove inflight call corre...

2017-08-08 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/3642

KafkaAdminClient should remove inflight call correctly after response is 
received



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-5710

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/3642.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3642






---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request #3621: KAFKA-5694; Add ChangeReplicaDirRequest and Descri...

2017-08-03 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/3621

KAFKA-5694; Add ChangeReplicaDirRequest and DescribeReplicaDirRequest 
(KIP-113)



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-5694

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/3621.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3621


commit 0c3262f53de8a99da0d1e2b6b7e817a4c570353b
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-08-02T19:10:07Z

KAFKA-5694; Add ChangeReplicaDirRequest and DescribeReplicaDirRequest 
(KIP-113)




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request #3614: KAFKA-5695; Test DeleteRecordsRequest in Authorize...

2017-08-02 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/3614

KAFKA-5695; Test DeleteRecordsRequest in AuthorizerIntegrationTest



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-5695

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/3614.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3614


commit 0abbf513b68e08613d14e6a1479fbe7dc7d372ec
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-08-03T04:54:52Z

KAFKA-5695; Test DeleteRecordsRequest in AuthorizerIntegrationTest




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request #3594: KAFKA-5663; Fix LogDirFailureTest system test

2017-07-28 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/3594

KAFKA-5663; Fix LogDirFailureTest system test



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-5663

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/3594.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3594


commit 1a2f429d4af2e0f77706cdcea1801f7ddc4195c8
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-07-28T21:55:44Z

KAFKA-5663; Fix LogDirFailureTest system test




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request #3583: KAFKA-5341; Add UnderMinIsrPartitionCount and per-...

2017-07-26 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/3583

KAFKA-5341; Add UnderMinIsrPartitionCount and per-partition UnderMinIsr 
metrics (KIP-164)



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-5341

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/3583.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3583


commit 93f541c249def6bdc158cb79592278d18cdf3ff8
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-05-28T08:10:28Z

KAFKA-5341; Add UnderMinIsrPartitionCount and per-partition UnderMinIsr 
metrics (KIP-164)




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request #3565: KAFKA-5627; Reduce classes needed for LeaderAndIsr...

2017-07-22 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/3565

KAFKA-5627; Reduce classes needed for LeaderAndIsrPartitionState and 
MetadataPartitionState



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-5627

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/3565.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3565


commit e42e6a2391313b66874d612195a1bf904f93e8d5
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-07-23T02:35:41Z

KAFKA-5627; Reduce classes needed for LeaderAndIsrPartitionState and 
MetadataPartitionState




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request #3528: Kafka-4763 (Used for triggering test only)

2017-07-21 Thread lindong28
Github user lindong28 closed the pull request at:

https://github.com/apache/kafka/pull/3528


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request #3528: Kafka-4763 (Used for triggering test only)

2017-07-14 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/3528

Kafka-4763 (Used for triggering test only)

This patch is used only for triggering test. No need for review.




You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-4763-test

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/3528.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3528


commit a7915c2d7b7b1a96ba78a4d814503356da5840e6
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-04-03T00:46:34Z

KAFKA-4763; Handle disk failure for JBOD (KIP-112)

commit 946ece0f2067c1a890d00714ac24f298d9dcc8b5
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-06-12T04:05:12Z

Address comments

commit f1e250b61a21ea74d895ff1c2d289a359c70f117
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-06-12T09:13:28Z

StopReplicaResponse should specify error if replica-to-be-deleted is not 
found and there is offline directory

commit 8f02b2b94a9acd016c7a88cb196f12abd3890960
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-06-13T20:15:58Z

Address comments

commit dc1d6f3c89595e6192833df3f780f9053bf9327e
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-06-17T02:35:18Z

Address comments

commit 7c531a273deab40fe5952377a85baf6aae286760
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-06-20T23:17:14Z

Address comments

commit 8bc60ab337ac65bf787c1fd47c4a3b5a65599d2c
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-06-21T20:27:09Z

Close file handler of all files in the offline log directory so that the 
disk can be umounted

commit 1f399a22c9af01e34c8cfa74aac413400f018ff0
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-06-23T00:41:21Z

Address comments

commit 633d4843fbcd6421d1bd488557f47c7edb8086d3
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-06-24T02:09:54Z

Catch and handle more IOExceptions

commit 5908e16c37846edc8870f3e0dc2e14634d5d0d24
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-06-28T00:31:34Z

Address comments

commit fa2edcac7217105706340d8594f409be1341c7b0
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-06-30T21:55:30Z

Address comments

commit d4a54dffd675fff9b7763ae4b4ffcc908c54f408
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-07-06T03:50:35Z

Address comments

commit b25a029970a8802d7fe50a69f23fc365ae146b7e
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-07-06T19:04:03Z

Replace _liveLogDirs.asScala.toSeq with _liveLogDirs.asScala.toArray to 
possibly reduce memory footprint

commit 522eff8ef2ae1f4235338335a7ef8657efa0e877
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-07-07T02:45:14Z

- Use LogDirFailureChannel to trigger handleLogDirFailure()
- Remove the newly-added metrics on shutdown()

commit 5bbb72ed3ca042aa731d756c03bd2e86a2ed5a42
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-07-07T22:06:47Z

- Add UNKNOWN_RETRIABLE.
- Convert KafkaStorageException to the error code of 
NotLeaderForPartitionException for existing versions of ProduceResponse and 
FetchResponse

commit e4404382f94754fb49bea4912e684d7e98e2e20c
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-07-13T18:21:29Z

Always return KafkaStorageException for replicas in offline log directories




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request #3498: Kafka-4763 (Used for triggering test only)

2017-07-07 Thread lindong28
Github user lindong28 closed the pull request at:

https://github.com/apache/kafka/pull/3498


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request #3498: Kafka-4763 (Used for triggering test only)

2017-07-07 Thread lindong28
GitHub user lindong28 reopened a pull request:

https://github.com/apache/kafka/pull/3498

Kafka-4763 (Used for triggering test only)

This patch is used only for triggering test. No need for review.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-4763-test

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/3498.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3498


commit b10e55ac5c83d0a356f79b0325d0dd8cefe00a42
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-04-03T00:46:34Z

KAFKA-4763; Handle disk failure for JBOD (KIP-112)

commit 0c97e0907e93c00fc23958478ec103f6ac49a48d
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-06-12T04:05:12Z

Address comments

commit c013a815d72fa85175dfee8816366a02323526e2
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-06-12T09:13:28Z

StopReplicaResponse should specify error if replica-to-be-deleted is not 
found and there is offline directory

commit 15ab857bb60755a1e5c296dabf59d1d43f44fc0f
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-06-13T20:15:58Z

Address comments

commit 563bf001b78662834e403619657f21415095d38c
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-06-17T02:35:18Z

Address comments

commit 94efa20ac5193b459ff33c4cbbf5118a17749354
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-06-20T23:17:14Z

Address comments

commit 96af4783655466f481d69a5852d1ddb678fde0d1
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-06-21T20:27:09Z

Close file handler of all files in the offline log directory so that the 
disk can be umounted

commit 6e80507cb507b07d7e8378a4e49e3b0273026d94
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-06-23T00:41:21Z

Address comments

commit ffc91298efa66eb02d365c5e198e033b8b098062
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-06-24T02:09:54Z

Catch and handle more IOExceptions

commit 785bd12618978b4771b30f7bafcd8b3bdf30a53c
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-06-28T00:31:34Z

Address comments

commit 4b2bb09d05c76e9e974334bfa5192e16b34a4d6b
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-07-07T08:22:21Z

checkpoint3




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request #3498: Kafka-4763 (Used for triggering test only)

2017-07-07 Thread lindong28
Github user lindong28 closed the pull request at:

https://github.com/apache/kafka/pull/3498


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request #3498: Kafka-4763 (Used for triggering test only)

2017-07-06 Thread lindong28
Github user lindong28 closed the pull request at:

https://github.com/apache/kafka/pull/3498


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request #3498: Kafka-4763 (Used for triggering test only)

2017-07-06 Thread lindong28
GitHub user lindong28 reopened a pull request:

https://github.com/apache/kafka/pull/3498

Kafka-4763 (Used for triggering test only)

This patch is used only for triggering test. No need for review.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-4763-test

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/3498.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3498


commit b10e55ac5c83d0a356f79b0325d0dd8cefe00a42
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-04-03T00:46:34Z

KAFKA-4763; Handle disk failure for JBOD (KIP-112)

commit 0c97e0907e93c00fc23958478ec103f6ac49a48d
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-06-12T04:05:12Z

Address comments

commit c013a815d72fa85175dfee8816366a02323526e2
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-06-12T09:13:28Z

StopReplicaResponse should specify error if replica-to-be-deleted is not 
found and there is offline directory

commit 15ab857bb60755a1e5c296dabf59d1d43f44fc0f
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-06-13T20:15:58Z

Address comments

commit 563bf001b78662834e403619657f21415095d38c
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-06-17T02:35:18Z

Address comments

commit 94efa20ac5193b459ff33c4cbbf5118a17749354
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-06-20T23:17:14Z

Address comments

commit 96af4783655466f481d69a5852d1ddb678fde0d1
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-06-21T20:27:09Z

Close file handler of all files in the offline log directory so that the 
disk can be umounted

commit 6e80507cb507b07d7e8378a4e49e3b0273026d94
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-06-23T00:41:21Z

Address comments

commit ffc91298efa66eb02d365c5e198e033b8b098062
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-06-24T02:09:54Z

Catch and handle more IOExceptions

commit 785bd12618978b4771b30f7bafcd8b3bdf30a53c
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-06-28T00:31:34Z

Address comments

commit 8b0b9c58c68958f8558304c8fce70fecf99b3b3c
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-06-30T21:55:30Z

Address comments




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request #3498: Kafka-4763 (Used for triggering test only)

2017-07-06 Thread lindong28
Github user lindong28 closed the pull request at:

https://github.com/apache/kafka/pull/3498


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request #3498: Kafka-4763 (Used for triggering test only)

2017-07-06 Thread lindong28
GitHub user lindong28 reopened a pull request:

https://github.com/apache/kafka/pull/3498

Kafka-4763 (Used for triggering test only)

This patch is used only for triggering test. No need for review.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-4763-test

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/3498.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3498


commit b10e55ac5c83d0a356f79b0325d0dd8cefe00a42
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-04-03T00:46:34Z

KAFKA-4763; Handle disk failure for JBOD (KIP-112)

commit 0c97e0907e93c00fc23958478ec103f6ac49a48d
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-06-12T04:05:12Z

Address comments

commit c013a815d72fa85175dfee8816366a02323526e2
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-06-12T09:13:28Z

StopReplicaResponse should specify error if replica-to-be-deleted is not 
found and there is offline directory

commit 15ab857bb60755a1e5c296dabf59d1d43f44fc0f
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-06-13T20:15:58Z

Address comments

commit 563bf001b78662834e403619657f21415095d38c
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-06-17T02:35:18Z

Address comments

commit 94efa20ac5193b459ff33c4cbbf5118a17749354
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-06-20T23:17:14Z

Address comments

commit 96af4783655466f481d69a5852d1ddb678fde0d1
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-06-21T20:27:09Z

Close file handler of all files in the offline log directory so that the 
disk can be umounted

commit 6e80507cb507b07d7e8378a4e49e3b0273026d94
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-06-23T00:41:21Z

Address comments




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request #3498: Kafka-4763 (Used for triggering test only)

2017-07-06 Thread lindong28
Github user lindong28 closed the pull request at:

https://github.com/apache/kafka/pull/3498


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request #3498: Kafka-4763 (Used for triggering test only)

2017-07-06 Thread lindong28
GitHub user lindong28 reopened a pull request:

https://github.com/apache/kafka/pull/3498

Kafka-4763 (Used for triggering test only)

This patch is used only for triggering test. No need for review.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-4763-test

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/3498.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3498


commit b10e55ac5c83d0a356f79b0325d0dd8cefe00a42
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-04-03T00:46:34Z

KAFKA-4763; Handle disk failure for JBOD (KIP-112)

commit 0c97e0907e93c00fc23958478ec103f6ac49a48d
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-06-12T04:05:12Z

Address comments

commit c013a815d72fa85175dfee8816366a02323526e2
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-06-12T09:13:28Z

StopReplicaResponse should specify error if replica-to-be-deleted is not 
found and there is offline directory

commit 15ab857bb60755a1e5c296dabf59d1d43f44fc0f
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-06-13T20:15:58Z

Address comments

commit 563bf001b78662834e403619657f21415095d38c
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-06-17T02:35:18Z

Address comments

commit 94efa20ac5193b459ff33c4cbbf5118a17749354
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-06-20T23:17:14Z

Address comments

commit 96af4783655466f481d69a5852d1ddb678fde0d1
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-06-21T20:27:09Z

Close file handler of all files in the offline log directory so that the 
disk can be umounted

commit 6e80507cb507b07d7e8378a4e49e3b0273026d94
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-06-23T00:41:21Z

Address comments




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request #3498: Kafka-4763 (Used for triggering test only)

2017-07-06 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/3498

Kafka-4763 (Used for triggering test only)

This patch is used only for triggering test. No need for review.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-4763-test

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/3498.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3498


commit b10e55ac5c83d0a356f79b0325d0dd8cefe00a42
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-04-03T00:46:34Z

KAFKA-4763; Handle disk failure for JBOD (KIP-112)

commit 0c97e0907e93c00fc23958478ec103f6ac49a48d
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-06-12T04:05:12Z

Address comments

commit c013a815d72fa85175dfee8816366a02323526e2
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-06-12T09:13:28Z

StopReplicaResponse should specify error if replica-to-be-deleted is not 
found and there is offline directory

commit 15ab857bb60755a1e5c296dabf59d1d43f44fc0f
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-06-13T20:15:58Z

Address comments

commit 563bf001b78662834e403619657f21415095d38c
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-06-17T02:35:18Z

Address comments

commit 94efa20ac5193b459ff33c4cbbf5118a17749354
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-06-20T23:17:14Z

Address comments

commit 96af4783655466f481d69a5852d1ddb678fde0d1
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-06-21T20:27:09Z

Close file handler of all files in the offline log directory so that the 
disk can be umounted

commit 6e80507cb507b07d7e8378a4e49e3b0273026d94
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-06-23T00:41:21Z

Address comments




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request #3463: KAFKA-5544; The LastStableOffsetLag metric should ...

2017-06-29 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/3463

KAFKA-5544; The LastStableOffsetLag metric should be removed when partition 
is deleted



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-5544

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/3463.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3463


commit 8798d2e4a0fcc9e8a71085d03659c870b1d8
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-06-30T03:16:06Z

KAFKA-5544; The LastStableOffsetLag metric should be removed when partition 
is deleted




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request #2929: KAFKA-4763; Handle disk failure for JBOD (KIP-112)

2017-04-27 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/2929

KAFKA-4763; Handle disk failure for JBOD (KIP-112)



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-4763

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/2929.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2929


commit ab6302b82b6245d1bbf8d77d836e362b95750ca4
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-04-03T00:46:34Z

KAFKA-4763; Handle disk failure for JBOD (KIP-112)




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request #2869: Update topic expiry time in Metadata every time th...

2017-04-18 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/2869

Update topic expiry time in Metadata every time the topic metadata is 
requested

As of current implementation, KafkaProducer.waitOnMetadata() will first 
reset topic expiry time of the topic before repeatedly sending 
TopicMetadataRequest and waiting for metadata response. However, if the 
metadata of the topic is not available within Metadata.TOPIC_EXPIRY_MS, which 
is set to 5 minutes, then the topic will be expired and removed from 
Metadata.topics. The TopicMetadataRequest will no longer include the topic and 
the KafkaProducer will never receive the metadata of this topic. It will enter 
an infinite loop of sending TopicMetadataRequest and waiting for metadata 
response.
This problem can be fixed by updating topic expiry time every time the 
topic metadata is requested.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-5086

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/2869.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2869


commit cdd239fbf3249ac746b17dc203ff40bcda56516c
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-04-19T04:07:48Z

Update topic expiry time in Metadata every time the topic metadata is 
requested




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request #2864: PartitionRecords.fetchRecords(...) should defer ex...

2017-04-17 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/2864

PartitionRecords.fetchRecords(...) should defer exception to the next call 
if iterator has already moved across any valid record



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-5078

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/2864.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2864


commit 4271a51c83e41e6b6620292b569d12b10b2eafa7
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-04-16T17:02:34Z

PartitionRecords.fetchRecords(...) should defer exception to the next call 
if
iterator has already moved across any valid record




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request #2859: KAFKA-5075; Defer exception to the next pollOnce()...

2017-04-15 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/2859

KAFKA-5075; Defer exception to the next pollOnce() if consumer's fetch 
position has already increased



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-5075

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/2859.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2859


commit a0d358396c94c6252790920fc80d42d60caf6289
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-04-15T22:42:26Z

KAFKA-5075; Defer exception to the next pollOnce() if consumer's fetch 
position has already increased




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request #2760: KAFKA-4973; Fix transient failure of AdminClientTe...

2017-03-29 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/2760

KAFKA-4973; Fix transient failure of 
AdminClientTest.testDeleteRecordsWithException



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-4973

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/2760.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2760


commit 71dbf02e45c0573af4bdda9f5864fbd749b56031
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-03-29T17:00:59Z

KAFKA-4973; Fix transient failure of 
AdminClientTest.testDeleteRecordsWithException




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request #1562: KAFKA-3908; Set ReceiveBufferSize for socket used ...

2017-03-08 Thread lindong28
Github user lindong28 closed the pull request at:

https://github.com/apache/kafka/pull/1562


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request #2641: KAFKA-4586 followup; Fix testMaxPollIntervalMsDela...

2017-03-05 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/2641

KAFKA-4586 followup; Fix testMaxPollIntervalMsDelayInRevocation test failure



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-4820-followup

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/2641.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2641


commit c1e429098f6c1dc3cd99c4ef1c0ba2a9662d7503
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-03-05T10:10:55Z

KAFKA-4586 followup; Fix testMaxPollIntervalMsDelayInRevocation test failure




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request #2619: KAFKA-4820; ConsumerNetworkClient.send() should no...

2017-02-28 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/2619

KAFKA-4820; ConsumerNetworkClient.send() should not require global lock



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-4820

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/2619.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2619


commit 6a06f25748e7ff47eae27a5e40e74b2d9ac746e9
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-03-01T04:15:11Z

KAFKA-4820; ConsumerNetworkClient.send() should not require global lock




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request #2504: KAFKA-4735; Fix deadlock issue during MM shutdown

2017-02-05 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/2504

KAFKA-4735; Fix deadlock issue during MM shutdown



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-4735

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/2504.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2504


commit b0049582bf72a6cda8a8e46641f7dce640fab5a1
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-02-05T10:18:55Z

KAFKA-4735; Fix deadlock issue during MM shutdown




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request #2476: KAFKA-4586; Add purgeDataBefore() API (KIP-107)

2017-01-31 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/2476

KAFKA-4586; Add purgeDataBefore() API (KIP-107)



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-4586

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/2476.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2476


commit 3546fcc17e9ed816dc50536e23af8d0df6369591
Author: Dong Lin <lindon...@gmail.com>
Date:   2017-01-27T17:51:06Z

KAFKA-4586; Add purgeDataBefore() API (KIP-107)




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request #2241: KAFKA-4521; MirrorMaker should flush all messages ...

2016-12-10 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/2241

KAFKA-4521; MirrorMaker should flush all messages before releasing 
partition ownership during rebalance



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-4521

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/2241.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2241


commit cdbd79189f1cdb53f93d014c9b9758a5941b8168
Author: Dong Lin <do...@linkedin.com>
Date:   2016-12-11T07:03:46Z

KAFKA-4521; MirrorMaker should flush all messages before releasing 
partition ownership during rebalance




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request #2167: KAFKA-4442; Controller should grab lock when it is...

2016-12-06 Thread lindong28
Github user lindong28 closed the pull request at:

https://github.com/apache/kafka/pull/2167


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request #2208: KAFKA-4485; Follower should be in the isr if its F...

2016-12-02 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/2208

KAFKA-4485; Follower should be in the isr if its FetchRequest has fetched 
up to the logEndOffset of leader



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-4485

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/2208.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2208


commit c2c24839708ac0e60214f69606813d7aeff6ed21
Author: Dong Lin <lindon...@gmail.com>
Date:   2016-12-03T03:32:59Z

KAFKA-4485; Follower should be in the isr if its FetchRequest has fetched 
up to the logEndOffset of leader




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request #2141: KAFKA-4444; Aggregate requests sent from controlle...

2016-11-28 Thread lindong28
Github user lindong28 closed the pull request at:

https://github.com/apache/kafka/pull/2141


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request #2170: KAFKA-4445; PreferredLeaderElectionCommand should ...

2016-11-24 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/2170

KAFKA-4445; PreferredLeaderElectionCommand should query zookeeper only once 
per topic



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFAK-4445

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/2170.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2170


commit e5bd956c070afe2c5ca72ea53a7baa25c62f257b
Author: Dong Lin <lindon...@gmail.com>
Date:   2016-11-25T06:01:53Z

KAFKA-4445; PreferredLeaderElectionCommand should query zookeeper only once 
per topic




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request #2168: KAFKA-4443; Controller should send UpdateMetadataR...

2016-11-24 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/2168

KAFKA-4443; Controller should send UpdateMetadataRequest prior to 
LeaderAndIsrRequest during failover



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-4443

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/2168.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2168


commit 4db70c9e9960c688932dda8d942ee2fedc459e1e
Author: Dong Lin <lindon...@gmail.com>
Date:   2016-11-25T04:21:50Z

KAFKA-4443; Controller should send UpdateMetadataRequest prior to 
LeaderAndIsrRequest during failover




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request #2169: KAFKA-4415; Reduce time to create and send Metadat...

2016-11-24 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/2169

KAFKA-4415; Reduce time to create and send MetadataUpdateRequest



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-4415-2nd

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/2169.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2169


commit 439f3bbbcb8503508939977df6d6243b3eecb2f0
Author: Dong Lin <lindon...@gmail.com>
Date:   2016-11-25T04:32:27Z

KAFKA-4415; Reduce time to create and send MetadataUpdateRequest




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request #2167: KAFKA-4442; Controller should grab lock when it is...

2016-11-24 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/2167

KAFKA-4442; Controller should grab lock when it is being initialized to 
avoid race condition



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-4442

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/2167.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2167


commit 16825e60963844ab0729bf290cfc9e6cee79932f
Author: Dong Lin <lindon...@gmail.com>
Date:   2016-11-25T04:07:09Z

KAFKA-4442; Controller should grab lock when it is being initialized to 
avoid race condition




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request #2155: KAFKA-4429; records-lag should be zero if FetchRes...

2016-11-21 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/2155

KAFKA-4429; records-lag should be zero if FetchResponse is empty



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-4429

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/2155.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2155


commit 0dbcf2c1357861606e5e7bcf5ee59d29bb1641f3
Author: Dong Lin <lindon...@gmail.com>
Date:   2016-11-22T00:38:20Z

KAFKA-4429; records-lag should be zero if FetchResponse is empty




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request #2148: KAFKA-4420; Group StopReplicaRequests for partitio...

2016-11-17 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/2148

KAFKA-4420; Group StopReplicaRequests for partitions on the same broker 
into one StopReplicaRequest



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-4420

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/2148.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2148


commit b342c62a0d3d2457789ff953eac5cd7abe1a5d7f
Author: Dong Lin <lindon...@gmail.com>
Date:   2016-11-18T00:54:12Z

KAFKA-4420; Group StopReplicaRequests for partitions on the same broker 
into one StopReplicaRequest




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request #2141: KAFKA-4415; Reduce time to create and send Metadat...

2016-11-15 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/2141

KAFKA-4415; Reduce time to create and send MetadataUpdateRequest



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-4415

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/2141.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2141


commit a317b6de574842298015121b8cd836512728141e
Author: Dong Lin <lindon...@gmail.com>
Date:   2016-11-16T05:30:03Z

KAFKA-4415; Reduce time to create and send MetadataUpdateRequest




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request #1851: KAFKA-4158; Reset quota to default value if quota ...

2016-09-13 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/1851

KAFKA-4158; Reset quota to default value if quota override is deleted



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-4158

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/1851.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1851


commit beb402041dd21a087f173e503e5ff7f7b016b98f
Author: Dong Lin <lindon...@gmail.com>
Date:   2016-09-13T17:37:16Z

KAFKA-4158; Reset quota to default value if quota override is deleted




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request #1562: KAFKA-3908; Set ReceiveBufferSize for socket used ...

2016-08-07 Thread lindong28
GitHub user lindong28 reopened a pull request:

https://github.com/apache/kafka/pull/1562

KAFKA-3908; Set ReceiveBufferSize for socket used by Processor



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-3908

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/1562.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1562


commit 9ad0909e8cfd821dd7cea19efdc6ce993f95ace7
Author: Dong Lin <lindon...@gmail.com>
Date:   2016-06-27T22:37:59Z

KAFKA-3908; Set SendBufferSize for socket used by Processor




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request #1562: KAFKA-3908; Set ReceiveBufferSize for socket used ...

2016-08-07 Thread lindong28
Github user lindong28 closed the pull request at:

https://github.com/apache/kafka/pull/1562


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request #755: KAFKA-3089; VerifiableProducer should do a clean sh...

2016-06-27 Thread lindong28
Github user lindong28 closed the pull request at:

https://github.com/apache/kafka/pull/755


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request #1562: KAFKA-3908; Set SendBufferSize for socket used by ...

2016-06-27 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/1562

KAFKA-3908; Set SendBufferSize for socket used by Processor



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-3908

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/1562.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1562


commit 9ad0909e8cfd821dd7cea19efdc6ce993f95ace7
Author: Dong Lin <lindon...@gmail.com>
Date:   2016-06-27T22:37:59Z

KAFKA-3908; Set SendBufferSize for socket used by Processor




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request: KAFKA-3330; Truncate log cleaner offset checkp...

2016-03-03 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/1009

KAFKA-3330; Truncate log cleaner offset checkpoint if the log is truncated

@becketqin Can you take a look?

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-3330

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/1009.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1009


commit 5fc32b4020198dfeabc6bba80d4657f7de20e169
Author: Dong Lin <lindon...@gmail.com>
Date:   2016-03-03T23:02:23Z

KAFKA-3330; Truncate log cleaner offset checkpoint if the log is truncated




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request: KAFKA-3089; VerifiableProducer should do a cle...

2016-01-11 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/755

KAFKA-3089; VerifiableProducer should do a clean shutdown in stop_node()



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-3089

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/755.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #755


commit 1fdf7dc454f17da2f8ca95e62953949bf7cc0e3d
Author: Dong Lin <lindon...@gmail.com>
Date:   2016-01-11T22:36:37Z

KAFKA-3089; VerifiableProducer should do a clean shutdown in stop_node()




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request: KAFKA-3045; ZkNodeChangeNotificationListener s...

2016-01-04 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/731

KAFKA-3045; ZkNodeChangeNotificationListener shouldn't log 
InterruptedException as error



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-3045

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/731.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #731


commit c140a114c4d86ef5ecc408f38a4640f3e8cef5f3
Author: Dong Lin <lindon...@gmail.com>
Date:   2016-01-05T02:23:30Z

KAFKA-3045; ZkNodeChangeNotificationListener shouldn't log interrupted 
exception as error




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request: Minor: Fix @link in MetricName comment

2015-12-09 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/651

Minor: Fix @link in MetricName comment



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka minor-fix-link-comment

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/651.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #651


commit aebb8c587fb437b20754078b8e1f5ba1bcc6f2d3
Author: Dong Lin <lindon...@gmail.com>
Date:   2015-12-09T18:01:36Z

Minor: Fix @link in MetricName comment




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request: MINOR - fix typo in index corruption warning m...

2015-12-01 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/606

MINOR - fix typo in index corruption warning message



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka minor-fix-typo

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/606.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #606


commit a7ee81430e833c783507e89e98fb5334014954f6
Author: Dong Lin <lindon...@gmail.com>
Date:   2015-12-01T09:36:13Z

MINOR - fix typo in warning message




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request: Minor - remove unused TimeUnit from MetricConf...

2015-11-29 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/600

Minor - remove unused TimeUnit from MetricConfig



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka minor

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/600.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #600


commit 28a52a463df3157430baa1061b2bd4de39408b9f
Author: Dong Lin <lindon...@gmail.com>
Date:   2015-11-29T21:40:05Z

remove unused TimeUnit from MetricConfig




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request: MINOR: KAFKA-2751 Improve documentation for lo...

2015-11-05 Thread lindong28
Github user lindong28 closed the pull request at:

https://github.com/apache/kafka/pull/437


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request: MINOR: KAFKA-2751 Improve documentation for lo...

2015-11-05 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/437

MINOR: KAFKA-2751 Improve documentation for log.retention.ms



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-2751

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/437.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #437


commit ecf417eb443fb5c587810361b7b84368673991f1
Author: Dong Lin <lindon...@gmail.com>
Date:   2015-11-05T22:53:16Z

MINOR: KAFKA-2751 Improve documentation for log.retention.ms




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request: KAFKA-2721; Avoid handling duplicate LeaderAnd...

2015-11-05 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/436

KAFKA-2721; Avoid handling duplicate LeaderAndISR requests



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-2721

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/436.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #436


commit eb62763d2e6ef04a013eb15e381278a84041abd2
Author: Dong Lin <lindon...@gmail.com>
Date:   2015-11-05T21:32:51Z

KAFKA-2721; Avoid handling duplicate LeaderAndISR requests




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request: KAFKA-2678; partition level lag metrics can be...

2015-10-21 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/346

KAFKA-2678; partition level lag metrics can be negative



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-2678

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/346.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #346


commit 966d3aed1a796ddafd202f9ab467a06d7b804d2b
Author: Dong Lin <lindon...@gmail.com>
Date:   2015-10-21T21:12:21Z

KAFKA-2678; partition level lag metrics can be negative




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request: KAFKA-2668; Add a metric that records the tota...

2015-10-18 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/328

KAFKA-2668; Add a metric that records the total number of metrics

@onurkaraman @becketqin Do you have time to review this patch? It addresses 
the ticket that @jjkoshy filed in KAFKA-2668.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-2668

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/328.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #328


commit 1e362e7f73934006b6e5cbc53f3d64c12598897c
Author: Dong Lin <lind...@cis.upenn.edu>
Date:   2015-10-19T05:34:58Z

KAFKA-2668; Add a metric that records the total number of metrics




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request: update the command to run a particular test me...

2015-10-17 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/326

update the command to run a particular test method in readme



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka minor-readme

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/326.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #326


commit 98d3a3e30692ae1805567892e0cc17819517c283
Author: Dong Lin <lind...@cis.upenn.edu>
Date:   2015-10-17T06:44:19Z

update the command to run a particular test method in readme




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request: KAFKA-2669; Fix LogCleanerIntegrationTest

2015-10-17 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/327

KAFKA-2669; Fix LogCleanerIntegrationTest

LogCleanerIntegrationTest calls LogCleaner.awaitCleaned() to wait until 
cleaner has processed up to given offset. However, existing awaitCleaned() 
implementation doesn't wait for this. This patch fix the problem.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-2669

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/327.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #327


commit 4e80bd95e906b0afb193d2870a351e86b7336a3b
Author: Dong Lin <lind...@cis.upenn.edu>
Date:   2015-10-17T09:17:34Z

KAFKA-2669; Fix LogCleanerIntegrationTest




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request: MINOR: update the command to run a particular ...

2015-10-17 Thread lindong28
Github user lindong28 closed the pull request at:

https://github.com/apache/kafka/pull/326


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request: KAFKA-2660; Correct cleanableRatio calculation

2015-10-15 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/316

KAFKA-2660; Correct cleanableRatio calculation

@onurkaraman Could you have a look? This is the patch I discussed with you.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-2660

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/316.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #316


commit a303ec9f87a7e1f331771a837aad03c0cf4797a5
Author: Dong Lin <lindon...@gmail.com>
Date:   2015-10-15T17:36:12Z

KAFKA-2660; Correct cleanableRatio calculation




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request: KAFKA-2621; nextOffsetMetadata should be chang...

2015-10-08 Thread lindong28
Github user lindong28 closed the pull request at:

https://github.com/apache/kafka/pull/286


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request: KAFKA-2621; nextOffsetMetadata should be chang...

2015-10-07 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/286

KAFKA-2621; nextOffsetMetadata should be changed after rolling a new log 
segment



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-2621

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/286.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #286


commit 609c17536001042edb91576f4fd288d160e9938a
Author: Dong Lin <lindon...@gmail.com>
Date:   2015-10-08T05:09:09Z

KAFKA-2621; nextOffsetMetadata should be changed after rolling a new log 
segment




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request: KAFKA-2527; System Test for Quotas in Ducktape

2015-10-06 Thread lindong28
GitHub user lindong28 reopened a pull request:

https://github.com/apache/kafka/pull/275

KAFKA-2527; System Test for Quotas in Ducktape

@granders Can you take a look at this quota system test?

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-2527

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/275.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #275


commit cf1a116e79df10e1425a41efa2a25ba013fb7e19
Author: Dong Lin <lindon...@gmail.com>
Date:   2015-10-05T07:07:01Z

KAFKA-2527; System Test for Quotas in Ducktape

commit 345b99705fe8c63798b0e7fe9e941bd22e4e1ad2
Author: Dong Lin <lindon...@gmail.com>
Date:   2015-10-05T21:35:56Z

adjust quota configuration

commit 28bd200713b2a34178cbae093c5ef85ef2370078
Author: Dong Lin <lindon...@gmail.com>
Date:   2015-10-06T02:00:12Z

JmxMixin will subclass object

commit 0d07fc73fb2776739d6a8f1de0e175afa86f7825
Author: Dong Lin <lindon...@gmail.com>
Date:   2015-10-06T04:44:30Z

support jmx query with arbitrary object name and attributes

commit c0fd7682212709ab6612afd8e27d1d531616a863
Author: Dong Lin <lindon...@gmail.com>
Date:   2015-10-06T16:17:43Z

jmx_object_name is required to use jmx tool

commit f7cfad50f47f2c367bf002a227185a42faf7486e
Author: Dong Lin <lindon...@gmail.com>
Date:   2015-10-06T17:07:30Z

adjust quota test configuration




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request: KAFKA-2527; System Test for Quotas in Ducktape

2015-10-06 Thread lindong28
Github user lindong28 closed the pull request at:

https://github.com/apache/kafka/pull/275


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request: KAFKA-2527; System Test for Quotas in Ducktape

2015-10-06 Thread lindong28
Github user lindong28 closed the pull request at:

https://github.com/apache/kafka/pull/275


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request: KAFKA-2527; System Test for Quotas in Ducktape

2015-10-06 Thread lindong28
GitHub user lindong28 reopened a pull request:

https://github.com/apache/kafka/pull/275

KAFKA-2527; System Test for Quotas in Ducktape

@granders Can you take a look at this quota system test?

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-2527

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/275.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #275


commit cf1a116e79df10e1425a41efa2a25ba013fb7e19
Author: Dong Lin <lindon...@gmail.com>
Date:   2015-10-05T07:07:01Z

KAFKA-2527; System Test for Quotas in Ducktape

commit 345b99705fe8c63798b0e7fe9e941bd22e4e1ad2
Author: Dong Lin <lindon...@gmail.com>
Date:   2015-10-05T21:35:56Z

adjust quota configuration

commit 28bd200713b2a34178cbae093c5ef85ef2370078
Author: Dong Lin <lindon...@gmail.com>
Date:   2015-10-06T02:00:12Z

JmxMixin will subclass object

commit 0d07fc73fb2776739d6a8f1de0e175afa86f7825
Author: Dong Lin <lindon...@gmail.com>
Date:   2015-10-06T04:44:30Z

support jmx query with arbitrary object name and attributes

commit c0fd7682212709ab6612afd8e27d1d531616a863
Author: Dong Lin <lindon...@gmail.com>
Date:   2015-10-06T16:17:43Z

jmx_object_name is required to use jmx tool

commit f7cfad50f47f2c367bf002a227185a42faf7486e
Author: Dong Lin <lindon...@gmail.com>
Date:   2015-10-06T17:07:30Z

adjust quota test configuration




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request: KAFKA-2527; System Test for Quotas in Ducktape

2015-10-05 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/275

KAFKA-2527; System Test for Quotas in Ducktape

@granders Can you take a look at this quota system test?

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-2527

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/275.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #275


commit cf1a116e79df10e1425a41efa2a25ba013fb7e19
Author: Dong Lin <lindon...@gmail.com>
Date:   2015-10-05T07:07:01Z

KAFKA-2527; System Test for Quotas in Ducktape




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request: KAFKA-2585; ConsoleConsumer should not hang in...

2015-09-27 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/247

KAFKA-2585; ConsoleConsumer should not hang infinitely upon exception



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-2585

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/247.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #247


commit ccd6826e8ab257c56e0994414c3cffc9aca387a9
Author: Dong Lin <lindon...@gmail.com>
Date:   2015-09-28T05:38:27Z

KAFKA-2585; ConsoleConsumer should not hang infinitely upon exception




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request: MINOR: Fix Vagrant setup script for use on Fed...

2015-09-25 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/246

MINOR: Fix Vagrant setup script for use on Fedora

I tested and verified that `vagrant --version | egrep -o "\d+\.\d+\.\d+"` 
works on Mac but failed on RedHad 6.4, while `vagrant --version | egrep -o 
"[0-9]\.[0-9]\.[0-9]"` works on both OS.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka Vagrant-setup-on-Fedora

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/246.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #246


commit 658e23c463caf94fecbeaf7547dfab5ff5a03990
Author: Dong Lin <lindon...@gmail.com>
Date:   2015-09-25T23:11:08Z

MINOR: Fix Vagrant setup script for use on Fedora




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request: add unit test for OffsetResetStrategyTest

2015-09-24 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/239

add unit test for OffsetResetStrategyTest



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-2390-followup

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/239.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #239


commit 39c4cfb89a04f975d1d23cd5d880c9dc37c4f9eb
Author: Dong Lin <lindon...@gmail.com>
Date:   2015-09-24T17:46:04Z

add unit test for OffsetResetStrategyTest




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request: KAFKA-2278; JmxTool should support querying al...

2015-08-31 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/181

KAFKA-2278; JmxTool should support querying all objects when object-n…

…ame is omitted

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-2278

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/181.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #181


commit 82cd911cc832a91ecae5bca2a9e2ca8bc7ff69e4
Author: Dong Lin <lindon...@gmail.com>
Date:   2015-08-31T22:53:22Z

KAFKA-2278; JmxTool should support querying all objects when object-name is 
omitted




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request: KAFKA-2332; Add quota metrics to old producer ...

2015-08-28 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/176

KAFKA-2332; Add quota metrics to old producer and consumer



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-2332

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/176.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #176


commit 8bd032e577a8d51bd2346f402ba96842c3a680dd
Author: Dong Lin lindon...@gmail.com
Date:   2015-08-28T20:23:14Z

KAFKA-2332; Add quota metrics to old producer and consumer




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request: KAFKA-2485; Allow producer performance to take...

2015-08-27 Thread lindong28
GitHub user lindong28 opened a pull request:

https://github.com/apache/kafka/pull/174

KAFKA-2485; Allow producer performance to take properties from a file…

… via --consumer.config command line parameter

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-2485

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/174.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #174


commit b612b17a97e86a9ed7b6405ff3151f9e00f49d1f
Author: Dong Lin lindon...@gmail.com
Date:   2015-08-28T00:10:10Z

KAFKA-2485; Allow producer performance to take properties from a file via 
--consumer.config command line parameter




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request: KAFKA-2436; log.retention.hours should be hono...

2015-08-17 Thread lindong28
GitHub user lindong28 reopened a pull request:

https://github.com/apache/kafka/pull/142

KAFKA-2436; log.retention.hours should be honored by LogManager



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lindong28/kafka KAFKA-2436

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/142.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #142


commit a713d45ad4ed59440be020cc6c74efbeb2bbe54b
Author: Dong Lin lindon...@gmail.com
Date:   2015-08-16T23:11:58Z

KAFKA-2436; log.retention.hours should be honored by LogManager

commit a8436f778bbdc498cdae741a74c33296065d0b21
Author: Dong Lin lindon...@gmail.com
Date:   2015-08-17T15:30:14Z

A few other configurations should also be propagated to LogManager

commit ea44479abf305aa6926a1f6b2592c52216aa334f
Author: Dong Lin lindon...@gmail.com
Date:   2015-08-17T17:31:47Z

remove unnecessary type conversion

commit d634339fbb4daa0dfe112c6beea0751878613fa2
Author: Dong Lin lindon...@gmail.com
Date:   2015-08-17T17:57:43Z

move logRetentionTimeMillis to the group of Log Configuration in code




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka pull request: KAFKA-2436; log.retention.hours should be hono...

2015-08-17 Thread lindong28
Github user lindong28 closed the pull request at:

https://github.com/apache/kafka/pull/142


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


  1   2   >