FutureAborter error, not listed in docs
Options
info-rchitect
Registered Posts: 169 ✭✭✭✭✭✭
Hi,
We have a partitioned scenario that looks to be failing, we think due to memory:
[2022/03/17-10:24:25.351] [ShortTaskExec-0] [INFO] [dku.future.aborter] - Executing abort on FutureAborter FutureAborter@1215237485,createdInThread=ActivityExecutor-56-56,forChildThread=false[2022/03/17-10:24:25.353] [ShortTaskExec-0] [INFO] [dku.future.aborter] - Executing abort on FutureAborter FutureAborter@1117218333,createdInThread=ActivityExecutor-56-56,forChildThread=true[2022/03/17-10:24:25.356] [ShortTaskExec-0] [INFO] [dku.future.aborter] - Executing abort on FutureAborter FutureAborter@127266859,createdInThread=FRT-65-FlowRunnable-65,forChildThread=true[2022/03/17-10:24:25.362] [ShortTaskExec-0] [INFO] [dku.future.aborter] - Executing abort on FutureAborter FutureAborter@933331409,createdInThread=FRT-65-FlowRunnable-65,forChildThread=true[2022/03/17-10:24:25.367] [ShortTaskExec-0] [INFO] [dku.future.aborter] - Executing abort on FutureAborter FutureAborter@911775055,createdInThread=FRT-65-FlowRunnable-65,forChildThread=true[2022/03/17-10:24:25.367] [ShortTaskExec-0] [INFO] [dku.future.aborter] - Executing abort on FutureAborter FutureAborter@1334229527,createdInThread=FRT-65-FlowRunnable-65,forChildThread=true[2022/03/17-10:24:25.367] [ShortTaskExec-0] [INFO] [dku.future.aborter] - Executing abort on FutureAborter FutureAborter@1740246884,createdInThread=FRT-65-FlowRunnable-65,forChildThread=true
What is a `FutureAborter`? Is this due to RAM per thread? If so, how can we adjust the RAM perthread?
thx
Operating system used: Windows 10
Tagged:
Answers
-
Hi,
This is not an error nor a failure, and this does not cause scenario to fail.
If you experience a scenario failure, please open a support ticket https://doc.dataiku.com/dss/latest/troubleshooting/obtaining-support.html and attach a scenario diagnosis: from the "Last runs" page of the scenario, click the failing run and click on "Download diagnosis"
Thanks,
-
OK thanks for the info. On partition jobs where we saw this we noticed we did not get all of the test processed as we expected.
