[ https://issues.apache.org/jira/browse/YARN-7200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17233777#comment-17233777 ]
Agshin Kazimli commented on YARN-7200: -------------------------------------- Keeping the old exit logic as it is and not changing any field or attribute signature, I have created second patch witch ensures the schedulerMetrics.tearDown() function call, which in turn closes the json file and stops the thread. > SLS generates a realtimetrack.json file but that file is missing the closing > ']' > -------------------------------------------------------------------------------- > > Key: YARN-7200 > URL: https://issues.apache.org/jira/browse/YARN-7200 > Project: Hadoop YARN > Issue Type: Bug > Components: scheduler-load-simulator > Reporter: Grant Sohn > Assignee: Agshin Kazimli > Priority: Minor > Labels: newbie, newbie++ > Attachments: YARN-7200-branch-trunk.patch, YARN-7200.002.patch, > realtimetrack.json, snemeth-testing-20201113.zip > > > File > hadoop-tools/hadoop-sls/src/main/java/org/apache/hadoop/yarn/sls/scheduler/SchedulerMetrics.java > shows: > {noformat} > void tearDown() throws Exception { > if (metricsLogBW != null) { > metricsLogBW.write("]"); > metricsLogBW.close(); > } > .... > {noformat} > So the exit logic is flawed. -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org