Github user asfgit closed the pull request at:
https://github.com/apache/samza/pull/333
---
Github user asfgit closed the pull request at:
https://github.com/apache/samza/pull/332
---
Hi,
We were finally able to find out why the job takes so long to start.
There was higher than normal network IO during job startup and so we
checked size of the checkpoint topic on disk and it was ~21GB.
We then restarted the Kafka node who was the leader for the checkpoint
topic, the topic disk
GitHub user prateekm opened a pull request:
https://github.com/apache/samza/pull/334
SAMZA-1464: Flushing a closed RocksDB store causes SIGSEGVs
Made RocksDB operations check if DB is still open to avoid segfaults.
You can merge this pull request into a Git repository by running:
Awesome that you have figured it out! Just a general notice: any logcompact
topic used in Samza may see this slow-down if the Kafka log cleaner thread
dies, which include checkpoint, coordinator stream, and changelog topics.
Best!
-Yi
On Thu, Oct 19, 2017 at 12:14 PM, XiaoChuan Yu wrote:
> Hi,
