Azure Data Lake U-SQL作业失败，并出现错误:JM_FinalMetadataOperationUserError [英] Azure Data Lake U-SQL job failing with error: JM_FinalMetadataOperationUserError

问题描述

我已经在Azure Data Lake上运行U-SQL作业以更新分区表，它们成功运行，但在最终定稿"失败. 错误为"JM_FinalMetadataOperationUserError"的阶段，堆栈跟踪如下:

I've been running U-SQL jobs on Azure Data Lake that update partitioned tables and they run successfully, but fail at the "Finalizing" phase with the error "JM_FinalMetadataOperationUserError", the stack trace is as follows:

Object ec2d8ab3-6df5-48eb-9169-daec48bf27a6.DeployedLogs.dbo.ConcurrentRecord__1__System.DateTime.FromBinary
(5246322962427387904 /* 2012-02-01T12:00:00.0000000Z */) 
already exists at Scope.MetadataService.Client.WcfBasedMetadataClient.ExecuteMetadataJob(MetadataJob mdJob) 
at MetaDataExecutor.RealMetaDataExecutor.Execute(MetadataJob job) 
at MetaDataExecutor.Committer.Commit(MetadataJob job)

错误消息指出:

The error message states:

Failed to write job meta-data due to user error

什么会导致此问题?是由于从表中添加/截断了值吗?

What can cause this problem? Is it due to the values being added/truncated from the table?

将不胜感激.

推荐答案

调查确定了根本原因是试图创建相同分区的两个脚本之间的竞争条件.看 http://stackoverflow.com/questions/37560454/azure-data-lake-u-sql-job-failing-with-error-jm-finalmetadataoperationusererror 以获取详细信息.

The investigation identified the root cause as a race condition between two scripts that were trying to create the same partition. See http://stackoverflow.com/questions/37560454/azure-data-lake-u-sql-job-failing-with-error-jm-finalmetadataoperationusererror for details.

这篇关于Azure Data Lake U-SQL作业失败，并出现错误:JM_FinalMetadataOperationUserError的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！