t; max.request.size = 1048576
> value.serializer = class org.apache.kafka.common.serial
> ization.ByteArraySerializer
> ssl.keymanager.algorithm = SunX509
> metrics.sample.window.ms = 3
> partitioner.class = class org.apache.kafka.clients.produ
> cer.inter
> entities other than the intended recipient is prohibited. If you received
> this in error, please contact the sender and delete the material from any
> computer.
>
--
<http://www.openbet.com/> Francesco laTorre
Senior Developer
T: +44 208 742 1600
+44 203 249 8394
E: fra
pics until Kafka 0.9.0.
> 4. Some other potential issues that may caused by log compaction. (e.g.
> KAFKA-2024).
>
> Jiangjie (Becket) Qin
>
>
>
> On Wed, Nov 2, 2016 at 5:55 AM, Francesco laTorre <
> francesco.lato...@openbet.com> wrote:
>
> > Hi,
>
Hi,
We want to enable log compaction on an existing topic (in production).
Is it a safe operation or there are things to take into consideration ?
Kafka version 0.8
Cheers,
Francesco
--
<http://www.openbet.com/> Francesco laTorre
Senior Developer
T: +44 208 742 1600
+44 203 249 8
Hi,
*get* /controller
is the way to go, thought there should have been children.
Cheers,
Francesco
On 13 September 2016 at 15:29, Francesco laTorre <
francesco.lato...@openbet.com> wrote:
> Hi,
>
> Anyone else finding this weird ?
>
> Cheers,
> Francesco
>
>
Hi,
Anyone else finding this weird ?
Cheers,
Francesco
On 12 September 2016 at 15:53, Francesco laTorre <
francesco.lato...@openbet.com> wrote:
> Hi guys,
>
> Pretty new to kafka and having sporadic issues with replication.
> Running Kafka *0.8.2.1 *:
>
> $>
Hi guys,
Pretty new to kafka and having sporadic issues with replication.
Running Kafka *0.8.2.1 *:
$> find ./libs/ -name \*kafka_\* | head -1 | grep -o '\kafka[^\n]*'
kafka_2.11-0.8.2.1-scaladoc.jar
on a cluster of *3 brokers* :
$> ./zookeeper-shell.sh localhost:19374
Connecting to localhost:1
