[
https://issues.apache.org/jira/browse/KAFKA-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13141257#comment-13141257
]
Jun Rao commented on KAFKA-180:
---
SimpleConsumeShell is still useful for debugging purpose.
[
https://issues.apache.org/jira/browse/KAFKA-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13141374#comment-13141374
]
Neha Narkhede commented on KAFKA-171:
-
You can check it into trunk. 0.7 is going off
There are several wait strategies. You will want to use spin lock in
production environments where you should have enough CPU cores anyway.
Remember, the 'real' work runs in another always running thread that
also uses a spin lock to wait for more work.
In dev environment or hosts that need to
Log errors for unrecognized config options
--
Key: KAFKA-181
URL: https://issues.apache.org/jira/browse/KAFKA-181
Project: Kafka
Issue Type: Improvement
Components: core
[
https://issues.apache.org/jira/browse/KAFKA-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13141517#comment-13141517
]
Jay Kreps commented on KAFKA-181:
-
Yes, please yes.
I recommend we create a Config object
Set a TCP connection timeout for the SimpleConsumer
---
Key: KAFKA-182
URL: https://issues.apache.org/jira/browse/KAFKA-182
Project: Kafka
Issue Type: Bug
Reporter: Jay Kreps
Log retention size and file size should be a long
-
Key: KAFKA-184
URL: https://issues.apache.org/jira/browse/KAFKA-184
Project: Kafka
Issue Type: Bug
Reporter: Joel Koshy
