Error Handling
Subscriptions
Subscription Length
me-client-identified-contact-resolver
The worker me-client-identified-contact-resolver is not coping with the load. The autoscaler configuration might need to be updated to allow for more replicas.
If urgent you can do this directly in k9s but if needed make sure to commit the change in git as well.
-
Launch
k9s --command hpafor the production enironment. -
Search for
me-client-identified-contact-resolver -
Edit the configuration and increase the maxReplicas property.
me-client-contact-id-writer
The worker me-client-contact-id-writer is not coping with the load. The autoscaler configuration might need to be updated to allow for more replicas.
If urgent you can do this directly in k9s but if needed make sure to commit the change in git as well.
-
Launch
k9s --command hpafor the production enironment. -
Search for
me-client-contact-id-writer -
Edit the configuration and increase the maxReplicas property.
me-client-anonymous-contact-resolver
The worker me-client-anonymous-contact-resolver is not coping with the load. The autoscaler configuration might need to be updated to allow for more replicas.
If urgent you can do this directly in k9s but if needed make sure to commit the change in git as well.
-
Launch
k9s --command hpafor the production enironment. -
Search for
me-client-anonymous-contact-resolver -
Edit the configuration and increase the maxReplicas property.
Expired Messages
me-client-contact-id-writer-expired
The me-client-contact-id-writer worker updates the contact-id in various places and something failed. Typically this would be the device in dynamo that could not be updated. Verify if the device exists by using the client-id and the app-code in the message to construct the UID and query for the device in DynamoDB.
For more information on what is failing search for errors in the me-client index in kibana.
If the expired messages failed due to a transient error they could simply moved back to the client-changes topic to be retried using the me-cli tool.
me-cli pubsub subscriptions dump -n me-client-contact-id-writer-expired
me-cli pubsub publish -t client-changes
me-client-identified-contact-resolver-expired
Messages could end up in the expired subscription if there is problem with the communication with either contact-data service.
For more information on what is failing search for errors in the me-client index in kibana.
If the expired messages failed due to a transient error they could simply moved back to the client-changes topic to be retried using the me-cli tool.
me-cli pubsub subscriptions dump -n me-client-identified-contact-resolver-expired
me-cli pubsub publish -t client-changes
me-client-anonymous-contact-resolver-expired
The me-client-anonymous-contact-resolver tries to resolve an existing anonymous contact based on the client-id and a special contact-field created along with the application. If no existing contact is found a new is created.
Messages could end up in the expired subscription if there is problem with the communication with either contact-data service or suite.
For more information on what is failing search for errors in the me-client index in kibana.
If the expired messages failed due to a transient error they could simply moved back to the client-changes topic to be retried using the me-cli tool.
me-cli pubsub subscriptions dump -n me-client-anonymous-contact-resolver-expired
me-cli pubsub publish -t client-changes