Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
Kafka >> mail # dev >> [jira] [Closed] (KAFKA-738) correlationId is not set in FetchRequest in AbstractFetcherThread


Copy link to this message
-
[jira] [Closed] (KAFKA-738) correlationId is not set in FetchRequest in AbstractFetcherThread

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

Neha Narkhede closed KAFKA-738.
-------------------------------

    
> correlationId is not set in FetchRequest in AbstractFetcherThread
> -----------------------------------------------------------------
>
>                 Key: KAFKA-738
>                 URL: https://issues.apache.org/jira/browse/KAFKA-738
>             Project: Kafka
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 0.8
>            Reporter: Jun Rao
>            Assignee: Jun Rao
>            Priority: Blocker
>              Labels: p2
>             Fix For: 0.8
>
>         Attachments: kafka-738.patch, kafka-738.patch, kafka-738_v2.patch, kafka-738_v3.patch
>
>
> correlationId is always 0 in FetchRequest in AbstractFetcherThread.

--
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

 
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB