Hi Steve,
Could you please shed more light on this? What section should I revisit? I
am using high-level consumer. So I am simply calling consumer.close() when
I am shutting down the process. Is there any other method to be called
before calling close()?
On Mon, Jul 9, 2018 at 5:58 PM Steve Tian
>From all cases I know so far (including RDBMS storage solution), RAID 10
has been the choice. Also, the replication you are mentioning is the s/w
replication nothing to do with RAID 0 setup.
On 11 July 2018 at 23:59, Ali Nazemian wrote:
> Thanks. As this proposal is not available for the vers
I meant because there is no actual Raid Controller for running Raid on
cloud, it is basically Software Based Raid [1].
[1] https://en.wikipedia.org/wiki/RAID#Software-based
On Thu, Jul 12, 2018 at 6:29 PM M. Manna wrote:
> From all cases I know so far (including RDBMS storage solution), RAID 1
It's a very good and important doc so I think you should read it all. You
should get some idea from sections like *Detecting Consumer Failures* and
*Multi-threaded Processing* for your case.
On Thu, Jul 12, 2018, 3:17 PM Shantanu Deshmukh
wrote:
> Hi Steve,
>
> Could you please shed more light
+1 non-binding
Built from source, ran tests, ran quickstart and check signatures
Thanks!
On Wed, Jul 11, 2018 at 10:48 PM, Jakub Scholz wrote:
> +1 (non-binbding) ... I built the RC2 from source, run tests and used it
> with several of my applications without any problems.
>
> Thanks & Regards
Hi,
I am doing some experiments with kafka-streams KGroupedTable
aggregation, and admittedly I am not wiping data properly on each
restart, partially because I also wonder what would happen if you
change a streams topology without doing a proper reset.
I've noticed that from time to time, kafka-s
Hi Vasily,
Thanks for the email.
To answer your question: you should reset the application basically any
time you change the topology. Some transitions are safe, but others will
result in data loss or corruption. Rather than try to reason about which is
which, it's much safer just to either reset
Ah great, thanks Gouzhang.
I also noticed a similar issue with state store metrics, where rate metrics for
each thread/task appear to be the total rate across all threads/tasks on that
instance.
In addition to that, though, I also see state store metrics for tasks that have
been migrated to an