locked
Azure Stream analytics error RRS feed

  • Question

  • Hello,

     I am working with Azure stream analytics  to produce aggregated data and I it was running smoothly.After some time I had to edit my query and I just removed a complete query and again started the stream analytics but at that point an error occurred. The error: "Stream Analytics job status changed for last user action [Start job 'iot01summary']." My query is:

    --Ouery for hour 
    WITH [data] AS

    SELECT 
                cast(BoardId as NVARCHAR(MAX)) as 'DeviceId', 
        cast(SensorId as NVARCHAR(MAX)) as 'SensorId',
        cast(SensorType as NVARCHAR(MAX)) as 'SensorType',
        System.timestamp as 'Datetime',
          AVG(cast(SensorValue as Float)) as 'Average',
          MAX(cast(SensorValue as Float)) as 'Maximum',
          MIN(cast(SensorValue as Float)) as 'Minimum',
    COUNT(*) as 'Sum',
    SensorDataType,
    Substring(System.TIMESTAMP,0,9) as 'date1',
    Substring(System.TIMESTAMP,11,11) as 'time1'
    FROM
    iot01input 
    GROUP BY 
    SensorId,BoardId,SensorType,SensorDataType, TumblingWindow(Hour,1)
    )

    SELECT
    *
    INTO
    iot01sqlhour
    FROM
    [data]
     
     -- Query for day
    SELECT 
    cast(BoardId as NVARCHAR(MAX)) as 'DeviceId', 
    cast(SensorId as NVARCHAR(MAX)) as 'SensorId',
    cast(SensorType as NVARCHAR(MAX)) as 'SensorType',
    System.timestamp as 'Datetime',
      AVG(cast(SensorValue as Float)) as 'Average',
      MAX(cast(SensorValue as Float)) as 'Maximum',
      MIN(cast(SensorValue as Float)) as 'Minimum'
    INTO 
      iot01sqlday
    FROM
      iot01input 
    GROUP BY 
    SensorId,BoardId,SensorType, TumblingWindow(Day,1)

     


    • Edited by sp111222 Tuesday, November 17, 2015 7:04 AM
    Tuesday, November 17, 2015 7:03 AM

Answers

  • Hi there, there are some status messages that are logged for each streaming job. unless the messages are of "Error" type, you may ignore those messages. For example, a job may be restarted automatically by runtime if it detects an issue with the job or if there is underlying OS/Azure updates being pushed.

    In this case, it is not clear to me if your job *stopped* producing output after this event or if you are curious to understand what this log event is and if you need to act on it or not. please clarify.

    If you go to Operations Logs for this job, if you see any error events, select each of them and at the bottom of the page, you will see a button to get more details. that will have more details and also, job Id, correlation id etc. if you can provide those, i can look up what is happening if this is still an issue.

    Thanks


    Venkat Chilakala


    Wednesday, December 2, 2015 8:49 PM