yarn application ID 增长达到10000后

Job, Task, and Task Attempt IDs

In Hadoop 2, MapReduce job IDs are generated from YARN application IDs that arecreated by the YARN resource manager.

The format of an application ID is composedof the time that the resource manager (not the application) started and an incrementingcounter maintained by the resource manager to uniquely identify the application to that instance of the resource manager.

So the application with this ID:

appllcation_1410450250506_0003

is the third (0003; application IDs are 1 -based) application run by the resource manager,which started at the time represented by the timestamp 1410450250506.

The counter is formatted with leading zeros to make IDs sort nicely —in directory listings, for example.

However, when the counter reaches 10000, it is not reset, resulting in longer application IDs (which don’t sort so well). The corresponding job ID is created simply by replacing the application prefix of an application ID with a job prefix:

job_1410450250506_0003

Tasks belong to a job, and their IDs are formed by replacing the job prefix of a job ID with a task prefix and adding a suffix to identify the task within the job. For example:

task_1410450250506_0003_n_000003

is the fourth (000003; task IDs are 0-based) map (n) task of the job with ID job_1410450250506_0003. The task IDs arc created for a job when it is initialized, so they do not necessarily dictate the order in which the tasks will be executed. Tasks may be executed more than once, due to failure (see MTask FailurcM on page 193) or speculative execution (see speculative Execution" on page 204), so to identify different instances of a task execution, task attempts are given unique IDs. For example:

attenpt_1410450256506_0003_n_000003_0

is the first (0; attempt IDs are O-based) attempt at running task

task_141045O250506_O003_m_000003.

Task attempts arc allocated during the job run as needed, so their ordering represents the order in which they were created to run.

简而言之,就是当yarn application id超过了4位数的范围,也就是达到10000后,yarn直接做增加位数操作,来扩展id空间范围。同时官方承认,这会导致根据id排序结果出现偏差。

Hadoop: The Definitive Guide: Storage and Analysis at Internet Scale

时间: 2024-09-30 06:41:32

yarn application ID 增长达到10000后的相关文章

spark-shell启动报错:Yarn application has already ended! It might have been killed or unable to launch application master

spark-shell不支持yarn cluster,以yarn client方式启动 spark-shell --master=yarn --deploy-mode=client 启动日志,错误信息如下 其中"Neither spark.yarn.jars nor spark.yarn.archive is set, falling back to uploading libraries under SPARK_HOME",只是一个警告,官方的解释如下: 大概是说:如果 spark.

Hibernate在oracle中ID增长的方式

引用链接:http://blog.csdn.net/w183705952/article/details/7367272 Hibernate在oracle中ID增长的方式 第一种:设置ID的增长策略是sequence,同时指定sequence的名字,最好每个表建一个sequence,此种做法就如同MS-SQL,MY-SQL中的自动增长一样,不需要创建触发器,具体的Oracle数据库脚本及hibernate配置文件如下: [1]oracle数据表的创建脚本: Java代码  CREATE TABL

eclipse 4 rcp开发: java.lang.RuntimeException: No application id has been found.

eclipse 4.2.x (June )rcp + E4:http://download.eclipse.org/e4/updates/0.12 自带windowbuilder 1.2 e4 css spy +e4 tools:建立一个默认的E4 application: 建立好后,直接执行: 错误详情: java.lang.RuntimeException: No application id has been found.at org.eclipse.equinox.internal.ap

从Resource Manager中获取一个新的Application ID

前提:有一个hadoop集群,并且拷贝core-site.xml,hdfs-site.xml,mapred-site.xml,yarn-site.xml到classpath下,可以使src/main/resources 1.获取一个GetNewApplicationRequest,实例是protobuf的类GetNewApplicationRequestPBImpl,未来会支持其他序列化方式.序列化方式决定了RPC工厂,产生哪种可序列化类. Records.newRecord,就是实例化一个pr

Android package属性、package name和Application ID三者的联系及区别

名词解释 package属性:在AndroidManifest.xml文件中. package name:应用程序的包名. Application ID:模块defaultConfig块下的applicationId属性. 设置Application ID 每个Android应用程序都有唯一一个类似Java包名的Application ID,比如com.example.myapp.在Android设备和Google应用商店上,Application ID是您应用的唯一标识.如果您想上传应用程序的

[JAVA][RCP]Clean project之后报错:java.lang.RuntimeException: No application id has been found.

Clean了一下Project,然后就报了如下错误 !ENTRY com.release.nattable.well_analysis 2 0 2015-11-20 17:04:44.609 !MESSAGE Could not resolve module: com.release.nattable.well_analysis [72] Unresolved requirement: Import-Package: org.eclipse.nebula.widgets.nattable.dat

Hibernate在oracle中ID增长的方式(续)

引用链接:http://blog.csdn.net/w183705952/article/details/7367272 第二种:设置ID的增长策略是native,但是需要创建一个名字为hibernate_sequence(这个名字好像是hibernate默认的sequence名字,不创建会出错的)的全局使用的sequence,然后再对每一个表的ID生成的时候,使用触发器,取得hibernate_sequence.CURRVAL作为新记录的ID,具体的oracle数据库脚本及hibernate配

ambari集群yarn任务不停增长的问题

这几天集群任务不停的增长,并且不是业务提交的任务,最后全部执行失败 Total number of applications (application-types: [] and states: [SUBMITTED, ACCEPTED, RUNNING]):6463 Application-Id Application-Name Application-Type User Queue State Final-State Progress Tracking-URLapplication_1527

关于php中id设置自增后不连续的问题

alter table tablename drop column id;alter table tablename add id mediumint(8) not null primary key auto_increment first; 每次删除把这两行家伙加上就行了 还有就是这个 使用mysqli对象中的query()方法每次调用只能执行一条SQL命令.如果需要一次执行多条SQL命令,就必须使用mysqli对象中的 multi_query()方法.具体做法是把多条SQL命令写在同一个字符