[
https://issues.apache.org/jira/browse/TEZ-2203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajesh Balamohan updated TEZ-2203:
----------------------------------
Comment: was deleted
(was: Minor comments.
- In GcTimeUpdater, should this be moved to constructor itself?
>>
TezCounter gcCounter = counters.findCounter(TaskCounter.GC_TIME_MILLIS);
>>
- In DAGAppMaster, cpuPlugin & GcTimeUpdater are always initialized; Do we need
the null check in getAMGCTime, getAMCPUTime?
- In DAGAppMaster, initResourceCalculatorPlugins() is called in serviceInit().
If user makes any mistake in configuring the plugin,
initResourceCalculatorPlugins() could get RuntimeException? Info might not be
available to end user to find out the reason for AM not starting (Could get
ExitCodeException exitCode=??)
)
> Intern strings in tez counters
> ------------------------------
>
> Key: TEZ-2203
> URL: https://issues.apache.org/jira/browse/TEZ-2203
> Project: Apache Tez
> Issue Type: Task
> Reporter: Bikas Saha
> Assignee: Bikas Saha
> Attachments: TEZ-2203.1.patch
>
>
> Getting per IO counters is possible today. This jira tracks work needed to
> enabled them by default. Internalizing strings to save memory is one item
> needed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
