Re: implementing kafka transactions : performance issue

2017-09-19 Thread Hugues . Deslandes
props.put(ProducerConfig.RETRIES_CONFIG , 5); > > > > props.put(ProducerConfig.ENABLE_IDEMPOTENCE_CONFIG,true); > > props.put(ProducerConfig.TRANSACTIONAL_ID_CONFIG, > > transactionnalId); > > props.put(ProducerConfig. > > MAX_IN_FLIGHT_REQUESTS_PER_CONNECTION,1); > > > > confluentProducer = new KafkaProducer<>(props); > > > > Any idea what could be wrong ? have I forgotten something ? > > Thanks > > Hugues DESLANDES > > > > > > > > > > > >

implementing kafka transactions : performance issue

2017-09-18 Thread Hugues . Deslandes
IGHT_REQUESTS_PER_CONNECTION,1); confluentProducer = new KafkaProducer<>(props); Any idea what could be wrong ? have I forgotten something ? Thanks Hugues DESLANDES

Re: State store and input topics with different number of partition

2017-09-05 Thread Hugues . Deslandes
er on second topic that will > trigger a query on statestore > option 2 : have 4 partitions for topic 2 and write the same message in the > 4 partitions > > I tested both but not sure which one is better ... > Do you have any other suggestions or comments > Thanks in advance. > > Hugues > [pièce jointe "signature.asc" supprimée par Hugues Deslandes/R et D/Hardis]

State store and input topics with different number of partition

2017-09-01 Thread Hugues . Deslandes
Hi, I'd like to have your comments on the problem I met while testing my app with kafka streams (0.10.2.1) Roughly, my stream app has 2 input topics : . the first one has 4 partitions (main data) . the second one has only one partition and receives messages from time to time At first, I suppo