[
https://issues.apache.org/jira/browse/KYLIN-3979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16841430#comment-16841430
]
Na Zhai commented on KYLIN-3979:
--------------------------------
Hi, [~jason.tang].
What's the command of cleaning that you used? If you only run the command like
this {code:bash}bin/metastore.sh clean{code} Kylin will not delete the file,
you should add the parameter '--delete true'. If you run the command like this
{code:bash}bin/metastore.sh clean --delete true{code} Kylin will delete the
file that was modified 30 days ago. You can set the number of days to keep
metadata resource by adding the “–jobThreshold 30(30 can be changed to any
number)" option.
> Job Fetcher caught a exception java.lang.IllegalArgumentException: there is
> no related output for job
> -----------------------------------------------------------------------------------------------------
>
> Key: KYLIN-3979
> URL: https://issues.apache.org/jira/browse/KYLIN-3979
> Project: Kylin
> Issue Type: Bug
> Components: Metadata
> Affects Versions: v2.6.1
> Reporter: tangyupeng
> Priority: Minor
>
> After Kylin restart, it failed to load job information through the "Monitor"
> tab. Use command 'metastore.sh clean' seems not working, Kylin still has the
> same problem. The log is attached here:
> {code:java}
> // code placeholder
> 2019-04-24 06:33:46,750 WARN [pool-9-thread-1]
> threadpool.DefaultFetcherRunner:99 : Job Fetcher caught a exception
> java.lang.IllegalArgumentException: there is no related output for job
> id:484b1cb1-54a7-1ded-3cf6-928686557585
> at com.google.common.base.Preconditions.checkArgument(Preconditions.java:92)
> at
> org.apache.kylin.job.execution.ExecutableManager.getOutputDigest(ExecutableManager.java:179)
> at
> org.apache.kylin.job.impl.threadpool.DefaultFetcherRunner.run(DefaultFetcherRunner.java:61)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> 2019-04-24 06:34:09,210 ERROR [http-bio-7070-exec-10]
> controller.JobController:89 :
> java.lang.NullPointerException
> at org.apache.kylin.rest.service.JobService$22.apply(JobService.java:1113)
> at org.apache.kylin.rest.service.JobService$22.apply(JobService.java:1107)
> at com.google.common.base.Predicates$AndPredicate.apply(Predicates.java:343)
> at com.google.common.collect.Iterators$7.computeNext(Iterators.java:702)
> ...
> at java.lang.Thread.run(Thread.java:748)
> 2019-04-24 06:34:09,212 ERROR [http-bio-7070-exec-10]
> controller.BasicController:63 :
> org.apache.kylin.rest.exception.InternalErrorException:
> java.lang.NullPointerException{code}
> The reason is that Job plan and Job output has consystent data. But "clean"
> command seems not clean up the unconsistent meta data.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
