Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]
Created on 10-15-2015 01:02 PM - edited 09-16-2022 02:44 AM
Looking at hitting allt he right API's for charge back scenario. In the following call to RM API's
http://192.168.245.131:8088/ws/v1/cluster/apps/application_1442459299785_0002
Output of call below
<app> <id>application_1442459299785_0002</id> <user>hive</user> <name>HIVE-521c0020-4786-4e55-8822-abe11a517ba1</name> <queue>default</queue> <state>FINISHED</state> <finalStatus>SUCCEEDED</finalStatus> <progress>100.0</progress> <trackingUI>History</trackingUI><trackingUrl> http://sandbox.hortonworks.com:8088/proxy/application_1442459299785_0002/ </trackingUrl> <diagnostics>null</diagnostics> <clusterId>1444871487358</clusterId> <applicationType>TEZ</applicationType> <applicationTags/> <startedTime>1442460228059</startedTime> <finishedTime>1442502311402</finishedTime> <elapsedTime>42083343</elapsedTime> <amContainerLogs> http://sandbox.hortonworks.com:8042/node/containerlogs/container_e17_1442459299785_0002_01_000001/hi... </amContainerLogs> <amHostHttpAddress>sandbox.hortonworks.com:8042</amHostHttpAddress> <allocatedMB>-1</allocatedMB> <allocatedVCores>-1</allocatedVCores> <runningContainers>-1</runningContainers> <memorySeconds>10540022</memorySeconds> <vcoreSeconds>42158</vcoreSeconds> <preemptedResourceMB>0</preemptedResourceMB> <preemptedResourceVCores>0</preemptedResourceVCores> <numNonAMContainerPreempted>0</numNonAMContainerPreempted> <numAMContainerPreempted>0</numAMContainerPreempted> <logAggregationStatus>NOT_START</logAggregationStatus> </app>
Created 10-26-2015 05:59 PM
Got this information from Sai Nukavarapu and wanted to add it back to the thread in case anyone else needs to have more context to these meanings.
- What MemorySeconds means and vCoreSeconds mean.
1. memorySeconds - The amount of memory the application has allocated (megabyte-seconds);
Aggregated amount of memory (in megabytes) the application has allocated X the number of seconds the application has been running.
2. The amount of CPU resources the application has allocated (virtual core-seconds)
Aggregated number of vcores that the application has allocated X the number of seconds the application has been running.
Created 10-15-2015 01:57 PM
Some information in this link is useful looking under this section
, but seems a little vague, with what the meanings are to the above output. Maybe the -1's are due to the application being completed already? Curious to get others thoughts on how or if they have done a similar scenario for charge back purposes before.
Created 10-15-2015 02:08 PM
Looks like it is because of the application being completed because when running there is much more detail in this output of this call. I think I'm ok at this point, but please share experiences
Created 10-26-2015 05:59 PM
Got this information from Sai Nukavarapu and wanted to add it back to the thread in case anyone else needs to have more context to these meanings.
- What MemorySeconds means and vCoreSeconds mean.
1. memorySeconds - The amount of memory the application has allocated (megabyte-seconds);
Aggregated amount of memory (in megabytes) the application has allocated X the number of seconds the application has been running.
2. The amount of CPU resources the application has allocated (virtual core-seconds)
Aggregated number of vcores that the application has allocated X the number of seconds the application has been running.