bq. 1 topic with replication factor 1
There is no fault tolerance for the above setup.
Related please read KIP-113 .
Cheers
On Mon, Sep 25, 2017 at 11:56 AM, Anu P wrote:
> Hi All,
>
> I would like to request inputs - pros and cons of setting up a 2 broker
> Kafka cluster in production.
>
>
Hi All,
I would like to request inputs - pros and cons of setting up a 2 broker
Kafka cluster in production.
Following is the proposed configuration:
- 3 zookeeper nodes, 2 kafka brokers in AWS.
- 1 topic with replication factor 1 and 4 partitions.
- Producer with "acks = all" and min.insync.repl
Thanks Jakub .. for your inputs & help in this !
I was able to get this to work last week..
On Thu, Sep 21, 2017 at 12:22 AM, Jakub Scholz wrote:
> Hi,
>
> If you want the Kafka broker to present the whole chain you have to use the
> chain when creating the PKCS12 file (use the chain instead of
Hi, is that the complete log? It looks like there might be 2 tasks that are
still restoring:
2017-09-22 14:08:09 DEBUG AssignedTasks:90 - stream-thread
[argyle-streams-fp-StreamThread-6] transitioning stream task 1_18 to
restoring
2017-09-22 14:08:09 DEBUG AssignedTasks:90 - stream-thread
[argyle-s
Thanks for following up Elliot. Good to know. :)
Ismael
On Mon, Sep 25, 2017 at 10:20 AM, Elliot Crosby-McCullough <
elliot.crosby-mccullo...@freeagent.com> wrote:
> We did a bunch of sampling to no particular aid, broadly speaking the
> answer was "it's doing a bunch of talking".
>
> For those
We did a bunch of sampling to no particular aid, broadly speaking the
answer was "it's doing a bunch of talking".
For those who might want to know what this was in the end, during part of
our previous debugging we enabled `javax.net.debug=all` and didn't twig
that that had no effect on the log4j l
