错误码= 16777237 [英] ErrorCode=16777237

查看:234
本文介绍了错误码= 16777237的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

您好,

解决方案

当您遇到作业失败时,您可以从群集端日志中了解更多信息。  通常,如果某些内容与查询处理中断,则会有一个重试6次的顶点,并且该顶点的每次运行都会有一些日志信息。
 例如:


 


通过使用Hpc作业管理器浏览找到JobID和失败的顶点ID,然后找到日志@


\\< ComputeNodeName> \HpcTemp \< MyUserName> \< JOBID> \< VertexInstanceID>


 


我希望您会发现反序列化错误消息,并且根本原因很可能是您的IQueryable类型与对FromDSC的调用不匹配


 


IQueryable< string> !=  。FromDsc< LineRecord>


你可能想要IQueryable< LineRecord>


 


如果没有立即修复它,请检查日志以获取进一步指向根本原因的信息。


顺便提一下,我们在规划中有一些功能这可能有助于在提交作业之前避免客户端的这种类型的不匹配。


-Mike。


Hi,

解决方案

When you get a job failure, you can probably learn more from the cluster-side logs.  Typically if something just breaks with the query processing, there will be a vertex that retries 6 times and each of the runs for that vertex will have some log info.  For example:

 

Find the JobID and the failing vertex ID by browsing with the Hpc Job Manager, then find the logs @

\\<ComputeNodeName>\HpcTemp\<MyUserName>\<JOBID>\<VertexInstanceID>

 

I expect that you will find deserialization error messages, and the root cause is most likely that you have a mismatch between your IQueryable type and the call to FromDSC

 

IQueryable<string> != .FromDsc<LineRecord>

You probably want to have IQueryable<LineRecord>

 

If that doesn't fix it immediately, please check the logs for further pointers to the root cause.

Incidentally, we have some features in planning that may assist to avoid this type of mismatch on the client side before job submission.

-mike.


这篇关于错误码= 16777237的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆