[jira] [Updated] (KYLIN-5246) long running job's log staying in mem, may cause job server oom
[ https://issues.apache.org/jira/browse/KYLIN-5246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liyang updated KYLIN-5246: -- Summary: long running job's log staying in mem, may cause job server oom (was: long running jobs may cause memory problems in the job server) > long running job's log staying in mem, may cause job server oom > --- > > Key: KYLIN-5246 > URL: https://issues.apache.org/jira/browse/KYLIN-5246 > Project: Kylin > Issue Type: Improvement > Components: Job Engine >Affects Versions: v4.0.1 >Reporter: zhaoliu >Priority: Minor > > {code:java} > CliCommandExecutor > > BufferedReader reader = new BufferedReader( > new InputStreamReader(proc.getInputStream(), > StandardCharsets.UTF_8)); > String line; > StringBuilder result = new StringBuilder(); > while ((line = reader.readLine()) != null && > !Thread.currentThread().isInterrupted()) { > result.append(line).append('\n'); > if (logAppender != null) { > logAppender.log(line); > } > } > {code} > job运行时间久,result 会非常大,可能会引起内存问题 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KYLIN-5246) long running job's log staying in mem, may cause job server oom
[ https://issues.apache.org/jira/browse/KYLIN-5246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shao Feng Shi updated KYLIN-5246: - Fix Version/s: v4.0.3 > long running job's log staying in mem, may cause job server oom > --- > > Key: KYLIN-5246 > URL: https://issues.apache.org/jira/browse/KYLIN-5246 > Project: Kylin > Issue Type: Improvement > Components: Job Engine >Affects Versions: v4.0.1 >Reporter: Liu Zhao >Priority: Minor > Fix For: v4.0.3 > > > {code:java} > CliCommandExecutor > > BufferedReader reader = new BufferedReader( > new InputStreamReader(proc.getInputStream(), > StandardCharsets.UTF_8)); > String line; > StringBuilder result = new StringBuilder(); > while ((line = reader.readLine()) != null && > !Thread.currentThread().isInterrupted()) { > result.append(line).append('\n'); > if (logAppender != null) { > logAppender.log(line); > } > } > {code} > job运行时间久,result 会非常大,可能会引起内存问题 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KYLIN-5246) Long running job's log staying in mem, may cause job server oom
[ https://issues.apache.org/jira/browse/KYLIN-5246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shao Feng Shi updated KYLIN-5246: - Summary: Long running job's log staying in mem, may cause job server oom (was: long running job's log staying in mem, may cause job server oom) > Long running job's log staying in mem, may cause job server oom > --- > > Key: KYLIN-5246 > URL: https://issues.apache.org/jira/browse/KYLIN-5246 > Project: Kylin > Issue Type: Improvement > Components: Job Engine >Affects Versions: v4.0.1 >Reporter: Liu Zhao >Priority: Minor > Fix For: v4.0.3 > > > {code:java} > CliCommandExecutor > > BufferedReader reader = new BufferedReader( > new InputStreamReader(proc.getInputStream(), > StandardCharsets.UTF_8)); > String line; > StringBuilder result = new StringBuilder(); > while ((line = reader.readLine()) != null && > !Thread.currentThread().isInterrupted()) { > result.append(line).append('\n'); > if (logAppender != null) { > logAppender.log(line); > } > } > {code} > job运行时间久,result 会非常大,可能会引起内存问题 -- This message was sent by Atlassian Jira (v8.20.10#820010)