Re: Review Request 14641: Patch for KAFKA-1086

[Guozhang Wang]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/14641/#review27005
---



core/src/main/scala/kafka/tools/GetOffsetShell.scala


I thought mkString is used to transfer an iterable to String, not vice 
versa?


- Guozhang Wang


On Oct. 15, 2013, 12:31 a.m., Neha Narkhede wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/14641/
> ---
> 
> (Updated Oct. 15, 2013, 12:31 a.m.)
> 
> 
> Review request for kafka.
> 
> 
> Bugs: KAFKA-1086
> https://issues.apache.org/jira/browse/KAFKA-1086
> 
> 
> Repository: kafka
> 
> 
> Description
> ---
> 
> Improved GetOffsetShell to query metadata automatically, add batch offset 
> request for all partitions of a topic and improve usability
> 
> 
> Diffs
> -
> 
>   core/src/main/scala/kafka/tools/GetOffsetShell.scala 
> 2b9438ae3a4da2c7f97e05fb26bc179fe48f137d 
> 
> Diff: https://reviews.apache.org/r/14641/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Neha Narkhede
> 
>

[jira] [Commented] (KAFKA-1087) Empty topic list causes consumer to fetch metadata of all topics

[Neha Narkhede (JIRA)]

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

Neha Narkhede commented on KAFKA-1087:
--

Checked into 0.8, could you please provide a patch for trunk as well?

> Empty topic list causes consumer to fetch metadata of all topics
> 
>
> Key: KAFKA-1087
> URL: https://issues.apache.org/jira/browse/KAFKA-1087
> Project: Kafka
>  Issue Type: Bug
>Affects Versions: 0.8
>Reporter: Swapnil Ghike
>Assignee: Swapnil Ghike
> Attachments: KAFKA-1087.patch
>
>
> The ClientUtils fetches metadata for all topics if the topic set is empty. 
> If the topic list of a consumer is empty, the following happens if a 
> rebalance is triggered:
> - The fetcher is restarted, fetcher.startConnections() starts a 
> LeaderFinderThread
> - LeaderFinderThread waits on a condition
> - fetcher.startConnections() signals the aforementioned condition
> - LeaderFinderThread obtains metadata for all topics since the topic list is 
> empty.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Commented] (KAFKA-1087) Empty topic list causes consumer to fetch metadata of all topics

[Neha Narkhede (JIRA)]

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

Neha Narkhede commented on KAFKA-1087:
--

Good catch, +1 !

> Empty topic list causes consumer to fetch metadata of all topics
> 
>
> Key: KAFKA-1087
> URL: https://issues.apache.org/jira/browse/KAFKA-1087
> Project: Kafka
>  Issue Type: Bug
>Affects Versions: 0.8
>Reporter: Swapnil Ghike
>Assignee: Swapnil Ghike
> Attachments: KAFKA-1087.patch
>
>
> The ClientUtils fetches metadata for all topics if the topic set is empty. 
> If the topic list of a consumer is empty, the following happens if a 
> rebalance is triggered:
> - The fetcher is restarted, fetcher.startConnections() starts a 
> LeaderFinderThread
> - LeaderFinderThread waits on a condition
> - fetcher.startConnections() signals the aforementioned condition
> - LeaderFinderThread obtains metadata for all topics since the topic list is 
> empty.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Commented] (KAFKA-1087) Empty topic list causes consumer to fetch metadata of all topics

[Guozhang Wang (JIRA)]

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

Guozhang Wang commented on KAFKA-1087:
--

Great find. +1

PS: Shall we actually enforce topic list as required parameters also besides 
this fix?

> Empty topic list causes consumer to fetch metadata of all topics
> 
>
> Key: KAFKA-1087
> URL: https://issues.apache.org/jira/browse/KAFKA-1087
> Project: Kafka
>  Issue Type: Bug
>Affects Versions: 0.8
>Reporter: Swapnil Ghike
>Assignee: Swapnil Ghike
> Attachments: KAFKA-1087.patch
>
>
> The ClientUtils fetches metadata for all topics if the topic set is empty. 
> If the topic list of a consumer is empty, the following happens if a 
> rebalance is triggered:
> - The fetcher is restarted, fetcher.startConnections() starts a 
> LeaderFinderThread
> - LeaderFinderThread waits on a condition
> - fetcher.startConnections() signals the aforementioned condition
> - LeaderFinderThread obtains metadata for all topics since the topic list is 
> empty.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Updated] (KAFKA-1087) Empty topic list causes consumer to fetch metadata of all topics

[Swapnil Ghike (JIRA)]

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

Swapnil Ghike updated KAFKA-1087:
-

Description: 
The ClientUtils fetches metadata for all topics if the topic set is empty. 

If the topic list of a consumer is empty, the following happens if a rebalance 
is triggered:
- The fetcher is restarted, fetcher.startConnections() starts a 
LeaderFinderThread
- LeaderFinderThread waits on a condition
- fetcher.startConnections() signals the aforementioned condition
- LeaderFinderThread obtains metadata for all topics since the topic list is 
empty.

  was:
The ClientUtils fetches metadata for all topics if the topic set is empty. 

If the topic list of a consumer is empty, the following happens if a rebalance 
is triggered:
- The fetcher is restarted, it starts a LeaderFinderThread
- LeaderFinderThread waits on a condition
- fetcher.startConnections() signals the aforementioned condition
- LeaderFinderThread obtains metadata for all topics since the topic list is 
empty.


> Empty topic list causes consumer to fetch metadata of all topics
> 
>
> Key: KAFKA-1087
> URL: https://issues.apache.org/jira/browse/KAFKA-1087
> Project: Kafka
>  Issue Type: Bug
>Affects Versions: 0.8
>Reporter: Swapnil Ghike
>Assignee: Swapnil Ghike
> Attachments: KAFKA-1087.patch
>
>
> The ClientUtils fetches metadata for all topics if the topic set is empty. 
> If the topic list of a consumer is empty, the following happens if a 
> rebalance is triggered:
> - The fetcher is restarted, fetcher.startConnections() starts a 
> LeaderFinderThread
> - LeaderFinderThread waits on a condition
> - fetcher.startConnections() signals the aforementioned condition
> - LeaderFinderThread obtains metadata for all topics since the topic list is 
> empty.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Updated] (KAFKA-1087) Empty topic list causes consumer to fetch metadata of all topics

[Swapnil Ghike (JIRA)]

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

Swapnil Ghike updated KAFKA-1087:
-

Description: 
The ClientUtils fetches metadata for all topics if the topic set is empty. 

If the topic list of a consumer is empty, the following happens if a rebalance 
is triggered:
- The fetcher is restarted, it starts a LeaderFinderThread
- LeaderFinderThread waits on a condition
- fetcher.startConnections() signals the aforementioned condition
- LeaderFinderThread obtains metadata for all topics since the topic list is 
empty.

  was:
The ClientUtils fetches metadata for all topics if the topic set is empty. 

If the topic list of a consumer is empty, the following happens if a rebalance 
is triggered:
- LeaderFinderThread waits on a condition
- The fetcher is restarted and it signals the aforementioned condition
- LeaderFinderThread obtains metadata for all topics since the topic list is 
empty.


> Empty topic list causes consumer to fetch metadata of all topics
> 
>
> Key: KAFKA-1087
> URL: https://issues.apache.org/jira/browse/KAFKA-1087
> Project: Kafka
>  Issue Type: Bug
>Affects Versions: 0.8
>Reporter: Swapnil Ghike
>Assignee: Swapnil Ghike
> Attachments: KAFKA-1087.patch
>
>
> The ClientUtils fetches metadata for all topics if the topic set is empty. 
> If the topic list of a consumer is empty, the following happens if a 
> rebalance is triggered:
> - The fetcher is restarted, it starts a LeaderFinderThread
> - LeaderFinderThread waits on a condition
> - fetcher.startConnections() signals the aforementioned condition
> - LeaderFinderThread obtains metadata for all topics since the topic list is 
> empty.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Comment Edited] (KAFKA-1086) Improve GetOffsetShell to find metadata automatically

[Neha Narkhede (JIRA)]

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

Neha Narkhede edited comment on KAFKA-1086 at 10/15/13 12:33 AM:
-

Created reviewboard https://reviews.apache.org/r/14641/ for trunk



was (Author: nehanarkhede):
Created reviewboard https://reviews.apache.org/r/14641/


> Improve GetOffsetShell to find metadata automatically
> -
>
> Key: KAFKA-1086
> URL: https://issues.apache.org/jira/browse/KAFKA-1086
> Project: Kafka
>  Issue Type: Improvement
>Affects Versions: 0.8
>Reporter: Neha Narkhede
>Assignee: Neha Narkhede
> Attachments: KAFKA-1086.patch, KAFKA-1086.patch
>
>
> GetOffsetShell needs to be improved to work well with 0.8. Currently, it 
> requires the user to manually plug in the right leader which also limits 
> finding the offsets for all partitions of a topic in bulk. 



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Updated] (KAFKA-1087) Empty topic list causes consumer to fetch metadata of all topics

[Swapnil Ghike (JIRA)]

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

Swapnil Ghike updated KAFKA-1087:
-

Attachment: KAFKA-1087.patch

Unit tests pass.

> Empty topic list causes consumer to fetch metadata of all topics
> 
>
> Key: KAFKA-1087
> URL: https://issues.apache.org/jira/browse/KAFKA-1087
> Project: Kafka
>  Issue Type: Bug
>Affects Versions: 0.8
>Reporter: Swapnil Ghike
>Assignee: Swapnil Ghike
> Attachments: KAFKA-1087.patch
>
>
> The ClientUtils fetches metadata for all topics if the topic set is empty. 
> If the topic list of a consumer is empty, the following happens if a 
> rebalance is triggered:
> - LeaderFinderThread waits on a condition
> - The fetcher is restarted and it signals the aforementioned condition
> - LeaderFinderThread obtains metadata for all topics since the topic list is 
> empty.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Updated] (KAFKA-1087) Empty topic list causes consumer to fetch metadata of all topics

[Swapnil Ghike (JIRA)]

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

Swapnil Ghike updated KAFKA-1087:
-

Affects Version/s: 0.8

> Empty topic list causes consumer to fetch metadata of all topics
> 
>
> Key: KAFKA-1087
> URL: https://issues.apache.org/jira/browse/KAFKA-1087
> Project: Kafka
>  Issue Type: Bug
>Affects Versions: 0.8
>Reporter: Swapnil Ghike
>Assignee: Swapnil Ghike
>
> The ClientUtils fetches metadata for all topics if the topic set is empty. 
> If the topic list of a consumer is empty, the following happens if a 
> rebalance is triggered:
> - LeaderFinderThread waits on a condition
> - The fetcher is restarted and it signals the aforementioned condition
> - LeaderFinderThread obtains metadata for all topics since the topic list is 
> empty.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Created] (KAFKA-1087) Empty topic list causes consumer to fetch metadata of all topics

[Swapnil Ghike (JIRA)]

Swapnil Ghike created KAFKA-1087:


 Summary: Empty topic list causes consumer to fetch metadata of all 
topics
 Key: KAFKA-1087
 URL: https://issues.apache.org/jira/browse/KAFKA-1087
 Project: Kafka
  Issue Type: Bug
Reporter: Swapnil Ghike
Assignee: Swapnil Ghike


The ClientUtils fetches metadata for all topics if the topic set is empty. 

If the topic list of a consumer is empty, the following happens if a rebalance 
is triggered:
- LeaderFinderThread waits on a condition
- The fetcher is restarted and it signals the aforementioned condition
- LeaderFinderThread obtains metadata for all topics since the topic list is 
empty.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Updated] (KAFKA-1086) Improve GetOffsetShell to find metadata automatically

[Neha Narkhede (JIRA)]

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

Neha Narkhede updated KAFKA-1086:
-

Attachment: KAFKA-1086.patch

> Improve GetOffsetShell to find metadata automatically
> -
>
> Key: KAFKA-1086
> URL: https://issues.apache.org/jira/browse/KAFKA-1086
> Project: Kafka
>  Issue Type: Improvement
>Affects Versions: 0.8
>Reporter: Neha Narkhede
>Assignee: Neha Narkhede
> Attachments: KAFKA-1086.patch, KAFKA-1086.patch
>
>
> GetOffsetShell needs to be improved to work well with 0.8. Currently, it 
> requires the user to manually plug in the right leader which also limits 
> finding the offsets for all partitions of a topic in bulk. 



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Commented] (KAFKA-1086) Improve GetOffsetShell to find metadata automatically

[Neha Narkhede (JIRA)]

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

Neha Narkhede commented on KAFKA-1086:
--

Created reviewboard https://reviews.apache.org/r/14641/


> Improve GetOffsetShell to find metadata automatically
> -
>
> Key: KAFKA-1086
> URL: https://issues.apache.org/jira/browse/KAFKA-1086
> Project: Kafka
>  Issue Type: Improvement
>Affects Versions: 0.8
>Reporter: Neha Narkhede
>Assignee: Neha Narkhede
> Attachments: KAFKA-1086.patch, KAFKA-1086.patch
>
>
> GetOffsetShell needs to be improved to work well with 0.8. Currently, it 
> requires the user to manually plug in the right leader which also limits 
> finding the offsets for all partitions of a topic in bulk. 



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Review Request 14641: Patch for KAFKA-1086

[Neha Narkhede]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/14641/
---

Review request for kafka.


Bugs: KAFKA-1086
https://issues.apache.org/jira/browse/KAFKA-1086


Repository: kafka


Description
---

Improved GetOffsetShell to query metadata automatically, add batch offset 
request for all partitions of a topic and improve usability


Diffs
-

  core/src/main/scala/kafka/tools/GetOffsetShell.scala 
2b9438ae3a4da2c7f97e05fb26bc179fe48f137d 

Diff: https://reviews.apache.org/r/14641/diff/


Testing
---


Thanks,

Neha Narkhede

[jira] [Commented] (KAFKA-1086) Improve GetOffsetShell to find metadata automatically

[Neha Narkhede (JIRA)]

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

Neha Narkhede commented on KAFKA-1086:
--

Created reviewboard https://reviews.apache.org/r/14638/


> Improve GetOffsetShell to find metadata automatically
> -
>
> Key: KAFKA-1086
> URL: https://issues.apache.org/jira/browse/KAFKA-1086
> Project: Kafka
>  Issue Type: Improvement
>Affects Versions: 0.8
>Reporter: Neha Narkhede
>Assignee: Neha Narkhede
> Attachments: KAFKA-1086.patch
>
>
> GetOffsetShell needs to be improved to work well with 0.8. Currently, it 
> requires the user to manually plug in the right leader which also limits 
> finding the offsets for all partitions of a topic in bulk. 



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Updated] (KAFKA-1086) Improve GetOffsetShell to find metadata automatically

[Neha Narkhede (JIRA)]

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

Neha Narkhede updated KAFKA-1086:
-

Attachment: KAFKA-1086.patch

> Improve GetOffsetShell to find metadata automatically
> -
>
> Key: KAFKA-1086
> URL: https://issues.apache.org/jira/browse/KAFKA-1086
> Project: Kafka
>  Issue Type: Improvement
>Affects Versions: 0.8
>Reporter: Neha Narkhede
>Assignee: Neha Narkhede
> Attachments: KAFKA-1086.patch
>
>
> GetOffsetShell needs to be improved to work well with 0.8. Currently, it 
> requires the user to manually plug in the right leader which also limits 
> finding the offsets for all partitions of a topic in bulk. 



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Review Request 14638: Patch for KAFKA-1086

[Neha Narkhede]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/14638/
---

Review request for kafka.


Bugs: KAFKA-1086
https://issues.apache.org/jira/browse/KAFKA-1086


Repository: kafka


Description
---

Improved GetOffsetShell to query metadata automatically, add batch offset 
request for all partitions of a topic and improve usability


Diffs
-

  core/src/main/scala/kafka/tools/GetOffsetShell.scala 
2b9438ae3a4da2c7f97e05fb26bc179fe48f137d 

Diff: https://reviews.apache.org/r/14638/diff/


Testing
---


Thanks,

Neha Narkhede

[jira] [Created] (KAFKA-1086) Improve GetOffsetShell to find metadata automatically

[Neha Narkhede (JIRA)]

Neha Narkhede created KAFKA-1086:


 Summary: Improve GetOffsetShell to find metadata automatically
 Key: KAFKA-1086
 URL: https://issues.apache.org/jira/browse/KAFKA-1086
 Project: Kafka
  Issue Type: Improvement
Affects Versions: 0.8
Reporter: Neha Narkhede
Assignee: Neha Narkhede


GetOffsetShell needs to be improved to work well with 0.8. Currently, it 
requires the user to manually plug in the right leader which also limits 
finding the offsets for all partitions of a topic in bulk. 



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] Subscription: outstanding kafka patches

[jira]

Issue Subscription
Filter: outstanding kafka patches (67 issues)
The list of outstanding kafka patches
Subscriber: kafka-mailing-list

Key Summary
KAFKA-1084  Validate properties for custom serializers
https://issues.apache.org/jira/browse/KAFKA-1084
KAFKA-1082  zkclient dies after UnknownHostException in zk reconnect
https://issues.apache.org/jira/browse/KAFKA-1082
KAFKA-1081  kafka-run-class.sh is broken
https://issues.apache.org/jira/browse/KAFKA-1081
KAFKA-1049  Encoder implementations are required to provide an undocumented 
constructor.
https://issues.apache.org/jira/browse/KAFKA-1049
KAFKA-1042  Fix segment flush logic
https://issues.apache.org/jira/browse/KAFKA-1042
KAFKA-1032  Messages sent to the old leader will be lost on broker GC resulted 
failure
https://issues.apache.org/jira/browse/KAFKA-1032
KAFKA-1020  Remove getAllReplicasOnBroker from KafkaController
https://issues.apache.org/jira/browse/KAFKA-1020
KAFKA-1012  Implement an Offset Manager and hook offset requests to it
https://issues.apache.org/jira/browse/KAFKA-1012
KAFKA-1011  Decompression and re-compression on MirrorMaker could result in 
messages being dropped in the pipeline
https://issues.apache.org/jira/browse/KAFKA-1011
KAFKA-1008  Unmap before resizing
https://issues.apache.org/jira/browse/KAFKA-1008
KAFKA-1005  kafka.perf.ConsumerPerformance not shutting down consumer
https://issues.apache.org/jira/browse/KAFKA-1005
KAFKA-1004  Handle topic event for trivial whitelist topic filters
https://issues.apache.org/jira/browse/KAFKA-1004
KAFKA-998   Producer should not retry on non-recoverable error codes
https://issues.apache.org/jira/browse/KAFKA-998
KAFKA-997   Provide a strict verification mode when reading configuration 
properties
https://issues.apache.org/jira/browse/KAFKA-997
KAFKA-996   Capitalize first letter for log entries
https://issues.apache.org/jira/browse/KAFKA-996
KAFKA-984   Avoid a full rebalance in cases when a new topic is discovered but 
container/broker set stay the same
https://issues.apache.org/jira/browse/KAFKA-984
KAFKA-976   Order-Preserving Mirror Maker Testcase
https://issues.apache.org/jira/browse/KAFKA-976
KAFKA-967   Use key range in ProducerPerformance
https://issues.apache.org/jira/browse/KAFKA-967
KAFKA-917   Expose zk.session.timeout.ms in console consumer
https://issues.apache.org/jira/browse/KAFKA-917
KAFKA-885   sbt package builds two kafka jars
https://issues.apache.org/jira/browse/KAFKA-885
KAFKA-881   Kafka broker not respecting log.roll.hours
https://issues.apache.org/jira/browse/KAFKA-881
KAFKA-873   Consider replacing zkclient with curator (with zkclient-bridge)
https://issues.apache.org/jira/browse/KAFKA-873
KAFKA-868   System Test - add test case for rolling controlled shutdown
https://issues.apache.org/jira/browse/KAFKA-868
KAFKA-863   System Test - update 0.7 version of kafka-run-class.sh for 
Migration Tool test cases
https://issues.apache.org/jira/browse/KAFKA-863
KAFKA-859   support basic auth protection of mx4j console
https://issues.apache.org/jira/browse/KAFKA-859
KAFKA-855   Ant+Ivy build for Kafka
https://issues.apache.org/jira/browse/KAFKA-855
KAFKA-854   Upgrade dependencies for 0.8
https://issues.apache.org/jira/browse/KAFKA-854
KAFKA-815   Improve SimpleConsumerShell to take in a max messages config option
https://issues.apache.org/jira/browse/KAFKA-815
KAFKA-745   Remove getShutdownReceive() and other kafka specific code from the 
RequestChannel
https://issues.apache.org/jira/browse/KAFKA-745
KAFKA-735   Add looping and JSON output for ConsumerOffsetChecker
https://issues.apache.org/jira/browse/KAFKA-735
KAFKA-717   scala 2.10 build support
https://issues.apache.org/jira/browse/KAFKA-717
KAFKA-686   0.8 Kafka broker should give a better error message when running 
against 0.7 zookeeper
https://issues.apache.org/jira/browse/KAFKA-686
KAFKA-674   Clean Shutdown Testing - Log segments checksums mismatch
https://issues.apache.org/jira/browse/KAFKA-674
KAFKA-652   Create testcases for clean shut-down
https://issues.apache.org/jira/browse/KAFKA-652
KAFKA-649   Cleanup log4j logging
https://issues.apache.org/jira/browse/KAFKA-649
KAFKA-645   Create a shell script to run System Test with DEBUG details and 
"tee" console output to a file
https://issues.apache.org/jira/browse/KAFKA-645
KAFKA-598   decouple fetch size from max message size
https://issues.apache.org/jira/browse/KAFKA-598
KAFKA-583   SimpleConsumerShell may receive less data inconsistently
https://issues.apache.org/jira/browse/KAFKA-583
KAFKA-559   Garbage collec