LateInputEvent突然发生 [英] LateInputEvent Suddenly Happening

查看:82
本文介绍了LateInputEvent突然发生的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有2个不同的EventHub作为两个不同的Stream Analytics作业的输入.

上周,我开始在其中一个中获取LateInputEvent,昨天我开始在另一个中获取LateInputEvent.任何作业或将数据发送到EventHub的服务都没有改变.我查看了WaterMark Delay指标,可以看到 它从不到10秒增加到40分钟以上.

对于两个Stream Analytics作业,SU%利用率均低于25%. Stream Analytics查询使用TIMESTAMP BY,但是该子句中使用的属性与EventEnqueuedTime之间的时间看起来很正常,但EventProcessedUtcTime却看起来很正常.

这是事件的样子:

    {  
      数据":22164765,
      "data2":"ZP25",
      "data3":"460917448",
      " DateTime":" 2019-01-23T16:43:00.0000000" ;,
      " EventProcessedUtcTime":" 2019-01-24T19:03:31.4901338Z" ;,
      " PartitionId:0:
      "EventEnqueuedUtcTime":"2019-01-23T21:43:00.4580000Z"
}

DateTime由TIMESTAMP BY使用,因此您可以看到值是01/23/19在4:43 pm(UTC-5),然后EventHub在01/23/19在9:43 pm(UTC)接收到它,然后将处理时间显示为将24小时后的7:03 pm(UTC)的01/24/19.

我所有的事件都这样到达,正如我所说,我们没有对提供给EventHub的服务,流分析上的查询或增加事件发生的频率进行任何更改.

有什么想法可以进一步调查这个奇怪的问题吗?

解决方案

要缩小问题的确切原因,请查看此故障排除指南:

https://docs.microsoft.com/zh-cn/azure/stream-analytics/stream-analytics-troubleshoot-input

这将帮助我们确定导致问题的原因.


I have 2 different EventHubs working as input for two different Stream Analytics jobs. 

Last week I started getting LateInputEvent in one of them, and yesterday I started getting it in the other one. Nothing has changed in any of the jobs, or the services sending data to the EventHubs. I looked at the WaterMark Delay metric and I can see how it went from less than 10 seconds to over 40 minutes. 

For both Stream Analytics Jobs SU % Utilization is under 25%. The Stream Analytics query uses TIMESTAMP BY but the time between the attribute used in that clausule and the EventEnqueuedTime looks normal, the EventProcessedUtcTime looks off though. 

This is how the events look like:

   {  
      "data":22164765,
      "data2":"ZP25",
      "data3":"460917448",
      "DateTime":"2019-01-23T16:43:00.0000000", 
      "EventProcessedUtcTime":"2019-01-24T19:03:31.4901338Z",
      "PartitionId":0,
      "EventEnqueuedUtcTime":"2019-01-23T21:43:00.4580000Z"
}

DateTime is used by TIMESTAMP BY so as you can see the value is 01/23/19 at 4:43pm (UTC-5), then the EventHub received it on 01/23/19 at 9:43pm (UTC), and then the processed time says 01/24/19 at 7:03pm (UTC) almost 24 hours later. 

All my events are arriving like that, and as I said, we didn't make any change on the service feeding the EventHubs, the query on the Stream Analytics or incremented the frequency of events. 

Any idea how to investigate more about this weird issue?

解决方案

Hi,

To narrow down to the exact cause of the issue, have a look at this troubleshooting guide :

https://docs.microsoft.com/en-us/azure/stream-analytics/stream-analytics-troubleshoot-input

This will help us identify what's causing the issue. 


这篇关于LateInputEvent突然发生的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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