Hi Rahul, As the error log says, the job container was killed by the NM after the map task used much more memory than allowed. However you can adjust cube level MR parameters "mapreduce.map.memory.mb" and "mapreduce.map.java.opts" with " kylin.job.mr.config.override " as item prefix to override the default configuration.
-----邮件原件----- 发件人: rahulsingh [mailto:[email protected]] 发送时间: 2017年3月8日 19:07 收件人: [email protected] 主题: Kylin job killed by admin hi all, A kylin job failed with message: killed by admin MAP capability required is more than the supported max container capability in the cluster. Killing the Job. mapResourceRequest: <memory:3072, vCores:1> maxContainerCapability:<memory:2250, vCores:32> Job received Kill while in RUNNING state. Thank You -- View this message in context: http://apache-kylin.74782.x6.nabble.com/Kylin-job-killed-by-admin-tp7390.html Sent from the Apache Kylin mailing list archive at Nabble.com. 本电子邮件可能为保密文件。如果阁下非电子邮件所指定之收件人，谨请立即通知本人。敬请阁下不要使用、保存、复印、打印、散布本电子邮件及其内容，或将其用于其他任何目的或向任何人披露。谢谢您的合作！ This communication is intended only for the addressee(s) and may contain information that is privileged and confidential. You are hereby notified that, if you are not an intended recipient listed above, or an authorized employee or agent of an addressee of this communication responsible for delivering e-mail messages to an intended recipient, any dissemination, distribution or reproduction of this communication (including any attachments hereto) is strictly prohibited. If you have received this communication in error, please notify us immediately by a reply e-mail addressed to the sender and permanently delete the original e-mail communication and any attachments from all storage devices without making or otherwise retaining a copy.
