Assert 1000 wlmquery-GetBurstState() == WLMQuery::RunOnBurst - burst state

Question

Since switching on auto WLM management overnight, we're seeing intermittent errors like the following:

```
[2019-06-13 13:44:59] [XX000][500310] [Amazon](500310) Invalid operation: Assert
[2019-06-13 13:44:59] Details:
[2019-06-13 13:44:59] -----------------------------------------------
[2019-06-13 13:44:59] error:  Assert
[2019-06-13 13:44:59] code:      1000
[2019-06-13 13:44:59] context:   wlmquery->GetBurstState() == WLMQuery::RunOnBurst - burst state: 5
[2019-06-13 13:44:59] query:     54255279
[2019-06-13 13:44:59] location:  workloadmanager.cpp:2057
[2019-06-13 13:44:59] process:   padbmaster [pid=8191]
[2019-06-13 13:44:59] -----------------------------------------------;
[2019-06-13 13:44:59] java.lang.RuntimeException: com.amazon.support.exceptions.ErrorException: [Amazon](500310) Invalid operation: Assert
[2019-06-13 13:44:59] Details:
[2019-06-13 13:44:59] -----------------------------------------------
[2019-06-13 13:44:59] error:  Assert
[2019-06-13 13:44:59] code:      1000
[2019-06-13 13:44:59] context:   wlmquery->GetBurstState() == WLMQuery::RunOnBurst - burst state: 5
[2019-06-13 13:44:59] query:     54255279
[2019-06-13 13:44:59] location:  workloadmanager.cpp:2057
[2019-06-13 13:44:59] process:   padbmaster [pid=8191]
[2019-06-13 13:44:59] -----------------------------------------------;
[2019-06-13 13:44:59] 	at com.amazon.redshift.client.messages.inbound.ErrorResponse.toErrorException(Unknown Source)
[2019-06-13 13:44:59] 	at com.amazon.redshift.client.PGMessagingContext.handleErrorResponse(Unknown Source)
[2019-06-13 13:44:59] 	at com.amazon.redshift.client.PGMessagingContext.handleMessage(Unknown Source)
[2019-06-13 13:44:59] 	at com.amazon.jdbc.communications.InboundMessagesPipeline.getNextMessageOfClass(Unknown Source)
[2019-06-13 13:44:59] 	at com.amazon.redshift.client.PGMessagingContext.doMoveToNextClass(Unknown Source)
[2019-06-13 13:44:59] 	at com.amazon.redshift.client.PGMessagingContext.getErrorResponse(Unknown Source)
[2019-06-13 13:44:59] 	at com.amazon.redshift.client.PGClient.handleErrorsScenario3(Unknown Source)
[2019-06-13 13:44:59] 	at com.amazon.redshift.client.PGClient.handleErrors(Unknown Source)
[2019-06-13 13:44:59] 	at com.amazon.redshift.client.PGClient.directExecute(Unknown Source)
[2019-06-13 13:44:59] 	at com.amazon.redshift.client.PGClient.directExecuteExtraMetadata(Unknown Source)
[2019-06-13 13:44:59] 	at com.amazon.redshift.dataengine.PGQueryExecutor.execute(Unknown Source)
[2019-06-13 13:44:59] 	at com.amazon.jdbc.common.SStatement.executeNoParams(Unknown Source)
[2019-06-13 13:44:59] 	at com.amazon.jdbc.common.SStatement.execute(Unknown Source)
[2019-06-13 13:44:59] 	in RemoteStatementImpl.execute(RemoteStatementImpl.java:78) (no stack trace)
```

This is happening on a variety of queries that previously ran without incident.  Any thoughts on how to troubleshoot and/or fix?  
  
Thanks

Answer

Hi BarkMBishop,  
  
For any assertion an immediate AWS support case is the best course of action and likely the fastest response if you have an AWS support contract.   
  
However, a post to the forum is helpful to rest of us customers for our awareness and to help us all get the customer count on the issue up to a more representative level.  
  
So thanks for posting here (too)!  
  
Regards,  
-Kurt

Answer

This seems to have been resolved in a recent update.  Marking as answered.

Answer

Thank you for bringing this to our attention. We're currently investigating. I will update this post when we have identified the issue.   
  
Please look for an update here or, alternatively, raise a case with AWS Support mentioning this post. They will be able to contact you directly with further follow up.

Assert 1000 wlmquery->GetBurstState() == WLMQuery::RunOnBurst - burst state

相關內容