Hi Jose,
I was trying to validate the output of CURLfor ssl enabled kafka as there
was issue with Kafka SSL while consumption through spark streaming. The
client keystore was corrupt.
I regenerated the certs and keystores. It worked fine.
Kind Regards,
Sachit Murarka
On Tue, Jan 19, 2021 at 5:39 PM Jose Manuel Vega Monroy <
jose.monroy@williamhill.com > wrote:
> @Sachit
>
> SEC_ERROR_UNTRUSTED_ISSUER --> problem with SSL certificate, unstrusted
>
> So you would need CA certificate which issued into truststore used by curl
> for calls to trust.
>
> Depending on OS could be in different location.
>
> But not sure what you trying to do, if you really interested on Kafka
> client connection than curl.
>
> Thanks
>
> < http://www.williamhill.com/ >
> < http://www.whenthefunstops.co.uk/ >
> Jose Manuel Vega Monroy
> Java Developer / Software Developer Engineer in Test
> D...
Posts
Hi,
Apache Software Foundation does not require code contributors
(non-committers) to sign CLA.
Contributions are considered to be under the Apache License. Committers
need to sign a CLA.
Thanks,
Manikumar
On Wed, Jan 20, 2021 at 7:53 PM Radoslava Zheleva < rzheleva@vmware.com >
wrote:
> Hello Team,
>
>
>
> May you please advise if the Apache Kafka project requires contributors to
> sign the ASF CLA?
>
> I have been going through the project's GitHub repo and the webpage and I
> am not able to confirm if signing of the ASF CLA is require or not.
>
> May you please advise? In case you are requiring contributors to sign the
> ASF CLA, may you please provide me with an URL to the documentation?
>
>
>
>
>
> Thanks,
>
>
>
> Radi
>
>
>
> *From: *Radoslava Zheleva < rzheleva@vmware.com >
> *Date: *Monday, January 18, 2021 at 6:03 PM
> *To: *"...
Hello Team, May you please advise if the Apache Kafka project requires contributors to sign the ASF CLA? I have been going through the project's GitHub repo and the webpage and I am not able to confirm if signing of the ASF CLA is require or not. May you please advise? In case you are requiring contributors to sign the ASF CLA, may you please provide me with an URL to the documentation? Thanks, Radi From: Radoslava Zheleva <rzheleva@vmware.com> Date: Monday, January 18, 2021 at 6:03 PM To: "users@kafka.apache.org" <users@kafka.apache.org> Cc: Lauren Britton <lbritton@vmware.com> Subject: Re: Apache Kafka project CLA requirement Hello Team, May you please look at my question below and advise? Thanks, Radi From: Radoslava Zheleva <rzheleva@vmware.com> Date: Thursday, January 14, 2021 at 4:33 PM To: "...
Hello,
I have observed several use cases similar to yours that are using Kafka /
Kafka Streams in production. That being said, your concerns are valid:
* Big messages: 5MB is indeed large, but not extremely big for Kafka. If it
is a single message of hundreds of MBs or over a GB then it's a bit
different handling story (and you may need to consider chunking it). You
would still need to make sure Kafka is configured right with
max.message.size etc to handle them, also you may need to tune your clients
on network sockets (like the buffer size, etc) for optimal networking
performance.
* External call in Streams: if the external service may be unavailable,
then your implementation should have a timeout scenario to either drop the
record or retry it later (some implementations would put it into a retry
queue, again stored as a Kafka topic, and then read from it later to
retry). Also note that Kafka Streams rely on consumer to poll the records,
and if that `poll` cal...
Is there also a way to avoid duplicates if the application consumer from
kafka topic and writes the events to database?
e.g. in case the application restarts while processing a batch read from
topic and few events already written to database, when application
restarts, those events are again consumed by another instance and written
back to database.
Could this behavior be avoided somehow without putting constraints on
database table?
On Wed, Jan 6, 2021 at 11:18 PM Matthias J. Sax < mjsax@apache.org > wrote:
> Well, that is exactly what I mean by "it depends on the state store
> implementation".
>
> For this case, you cannot get exactly-once.
>
> There are actually ideas to improve the implementation to support the
> case you describe, but there is no timeline for this change yet. Not
> even sure if there is already a Jira ticket...
>
>
> -Matthias
>
> On 1/6/21 2:32 AM, Pushkar Deole wrote:
> > Th...
I'm new to Kafka and will be grateful for any advice We are updating a
legacy application together with moving it from IBM MQ to something
different.
Application currently does the following:
* Reads batch XML messages (up to 5 MB)
* Parses it to something meaningful
* Processes data parallelizing this procedure somehow manually for
parts of the batch. Involves some external legacy API calls
resulting in DB changes
* Sends several kinds of email notifications
* Sends some reply to some other queue
* input messages are profiled to disk
We are considering using Kafka with Kafka Streams as it is nice to
* Scale processing easily
* Have messages persistently stored out of the box
* Built-in partitioning, replication, and fault-tolerance
* Confluent Schema Registry to let us move to schema-on-write
* Can be used for service-to-service communication for other
applications as well
But I have some concerns.
We are ...
@Sachit
SEC_ERROR_UNTRUSTED_ISSUER --> problem with SSL certificate, unstrusted
So you would need CA certificate which issued into truststore used by curl for calls to trust.
Depending on OS could be in different location.
But not sure what you trying to do, if you really interested on Kafka client connection than curl.
Thanks
< http://www.williamhill.com/ >
< http://www.whenthefunstops.co.uk/ >
Jose Manuel Vega Monroy
Java Developer / Software Developer Engineer in Test
Direct: +0035 0 2008038 (Ext. 8038)
Email: jose.monroy@williamhill.com
William Hill | 6/1 Waterport Place | Gibraltar | GX11 1AA
On 19/01/2021, 09:44, "Sachit Murarka" < connectsachit@gmail.com > wrote:
Hello All,
I am doing curl o <host>:<port> of kafka. It is throwing below error post
applying SSL. Can you please check?
NSS error -8172 (SEC_ERROR_UNTRUSTED_ISSUER)
* Peer's certificate issuer has been mar...