Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Kafka >> mail # dev >> [jira] [Updated] (KAFKA-718) kafka-run-class.sh should use reasonable gc settings

Copy link to this message
[jira] [Updated] (KAFKA-718) kafka-run-class.sh should use reasonable gc settings

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

Jay Kreps updated KAFKA-718:

    Attachment: KAFKA-718-v2.patch

Hey Ashwanth, thanks for the patch.

I applied it to 0.8 and I want to abuse this ticket to include a bunch of trivial "good housekeeping" fixes I think we need for the 0.8 final release that probably don't warrant a ticket of thier own.

This includes:
1. Your gc settings, but minus the +AggressiveOpts which doesn't seem to work on all versions of java 1.6
2. Clean up the README which has a number of outdated things in it.
3. Remove unused properties from server.properties to fix WARN messages.
4. Change to use log.dirs in the example server config so people know about multiple log directories
5. Remove incorrect description of flush.interval in example server config.
> kafka-run-class.sh should use reasonable gc settings
> ----------------------------------------------------
>                 Key: KAFKA-718
>                 URL: https://issues.apache.org/jira/browse/KAFKA-718
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Jay Kreps
>            Assignee: Neha Narkhede
>         Attachments: 718-v1.patch, KAFKA-718-v2.patch
> Our start script seems to use the default "stop the world" collector. It would be good to default to well tuned gc settings including gc logging, CMS, etc. Whatever we are using in prod and perf lab...
> Many people who want to use kafka basically don't know java well so they won't succeed in figuring this stuff out on their own and just think it is broken and timing out if we don't have good defaults.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira