Checked Java DNS resolution caching:
```
sun.net.InetAddressCachePolicy.get();
sun.net.InetAddressCachePolicy.getNegative();
```
and those return 30 and 10 respectively. So it seems fine and it shouldn't
cache for too long.
On 2021/05/14 12:55:00, Michał Łowicki wrote:
> Hey,
>
> Had inciden
Don't think you cannot attach diagrams in these mailling lists.
On Thu, May 26, 2016 at 7:35 PM, Navneet Kumar wrote:
> Hi
> We are facing a issue where our Consumer component is not instantly
> logging the records in DB polled from the Brokers. We have following
> theOur architecture diagram is
Hi
We are facing a issue where our Consumer component is not instantly
logging the records in DB polled from the Brokers. We have following
theOur architecture diagram is attached herewith. Following are the
properties
configured:
Producer.properties
bootstrap.servers=xx.xxx.xxx.140:9092,xx.xxx.x
We have added the client public certs into broker truststore and vice
versa. We removed the keystone related properties from client code and
tried with ssl.client.auth as requested and none as well. We are still
getting same error. Please let us know what else we can use to try
On Fri, Feb 19, 201
Did you try what Adam is suggesting in the earlier email. Also to
quickly check you can try remove keystore and key.password configs from
client side.
-Harsha
On Thu, Feb 18, 2016, at 02:49 PM, Srikrishna Alla wrote:
> Hi,
>
> We are getting the below error when trying to use a Java new producer
That was a typo. I did remove that and still same error.
Thanks,
Sri
> On Feb 18, 2016, at 4:21 PM, Adam Kunicki wrote:
>
> Ha! nice catch Gwen!
>
>> On Thu, Feb 18, 2016 at 3:20 PM, Gwen Shapira wrote:
>>
>> props.put("ssl.protocal", "SSL"); <- looks like a typo.
>>
>> On Thu, Feb 18,
Ha! nice catch Gwen!
On Thu, Feb 18, 2016 at 3:20 PM, Gwen Shapira wrote:
> props.put("ssl.protocal", "SSL"); <- looks like a typo.
>
> On Thu, Feb 18, 2016 at 2:49 PM, Srikrishna Alla <
> srikrishna.a...@aexp.com.invalid> wrote:
>
> > Hi,
> >
> > We are getting the below error when trying
Just to be thorough, it seems you have client authentication enabled as
well.
This means that each broker must have your client's public certificate in
its truststore.
I felt like it might be easier to draw a diagram than write it out, but
this is what your setup should look like:
[image: Inline
props.put("ssl.protocal", "SSL"); <- looks like a typo.
On Thu, Feb 18, 2016 at 2:49 PM, Srikrishna Alla <
srikrishna.a...@aexp.com.invalid> wrote:
> Hi,
>
> We are getting the below error when trying to use a Java new producer
> client. Please let us know the reason for this error -
>
> Err
Looks like you might have bootstrap.servers pointed at Zookeeper. It should
point to the Kafka brokers instead. The behavior of poll() currently is to
block until the group's coordinator is found, but sending the wrong kind of
request to Zookeeper probably results in a server-side disconnect. In th
We haven't really measured the scala overhead. However, my guess is that it
should be small compared to the network overhead, which one has to pay for
each request.
Thanks,
Jun
On Fri, Dec 28, 2012 at 7:04 PM, S Ahmed wrote:
> Since kafka is written in scala, when using a java client (producer
11 matches
Mail list logo
