My apologies, I made mistake, the order in which Kafka server handle requests has no problem. Thanks.
2013/11/21 Jun Rao <jun...@gmail.com> > Does the built-in java client have the same problem? > > Thanks, > > Jun > > > On Wed, Nov 20, 2013 at 7:00 PM, 小宇 <mocking...@gmail.com> wrote: > > > Yes, it is reproducible. I have reported it in Jira: > > https://issues.apache.org/jira/browse/KAFKA-1137 . BTW, we meet this > > problem when wirte a Node.js Client of Kafka0.8 , > > https://github.com/SOHU-Co/kafka-node. > > > > Thanks. > > > > 2013/11/20 Jun Rao <jun...@gmail.com> > > > > > That sounds like a bug. Is that reproducible? If so, could you file a > > jira? > > > > > > Thanks, > > > > > > Jun > > > > > > > > > On Wed, Nov 20, 2013 at 12:05 AM, 小宇 <mocking...@gmail.com> wrote: > > > > > > > Hi, > > > > I am now using kafka0.8, i have problem with FetchRequest API ( > > > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/KAFKA/A+Guide+To+The+Kafka+Protocol#AGuideToTheKafkaProtocol-FetchRequest > > > > ), > > > > the detail of the problem as follow: > > > > I send two FetchRequest [topic, partition, maxWaitTime] through 1 > > socket > > > > connection, minBytes is set 1, each request hold a different topic > > > (topic1 > > > > and topic2), the maxWatiTime are same(30 seconds), as we know, if a > > topic > > > > (topic1) have new produced message, kafka server should write back > data > > > to > > > > the socket immediately, but the fact is server write back data only > > when > > > > topic2 has new message, otherwise i have to wait 30s to get the new > > > message > > > > in topic1.Is this a bug of kafka server , or it was designed like > this? > > > > > > > > Thanks. > > > > > > > > > >
