[BUG]: DMA not deleting entry for retries from Redis upon receiving ACK from vehicle

[kaushalaroraharman]

What happened?

for road-clearance component we will have DMARetryHandler, and if we send RoadClearanceMetadataResponse event to simulator we will received one Ack from simulator, so if we don`t received this Ack, then will trigger this DMARetryHandler to retry that send RoadClearanceMetadataResponse event to simulator.
And now on EMEA INT env, we already received that Ack, But there still triggered this DMARetryHandler to do the retry operation, so please help to check this DMA retry issue.

Versions

1.0.0, 1.1.0

Relevant log output

1.V2C RoadClearanceMetadataResponse event received with key as deviceID i.e T00000000000150
06:37:14.894 [road-clearance-sp-ca0b9a99-b453-4c63-887d-aca8af55d46d-StreamThread-1] DEBUG-Processing ignite Key:IgniteStringKey [key=T00000000000150], ignite value:IgniteEventImpl [getNestedEvents()=[], getEventId()=RoadClearanceMetadataResponse, getVersion()=1.0, getTimestamp()=1745735834867, getEventData()=RoadClearanceMetadataResponseV1_0{data=RoadClearanceMetadataResponseData{catalogVersion=9, catalogTimestamp=1742947931807, tileMetadataList=[]}, responseCode='RC_SUCCESS', failedTileList=FailedTileList{failedTileIds=[]}, noEventTileList=NoEventTileList{noEventTileIds=[121212132]}}, getRequestId()=null, getSourceDeviceId()=null, getVehicleId()=T0000000000000150, getSchemaVersion()=1.0, getDFFQualifier()=null, getTargetDeviceId()=Optional.empty, getMessageId()=600001, getCorrelationId()=31, getBizTransactionId()=ADROADCLEARANCE3fd1c3eec8fbad8c, isDeviceRoutable()=true, toString()=AbstractIgniteEvent [timezone=0, dffQualifier=null, targetDeviceId=null, messageId=600001, correlationId=31, bizTransactionId=ADROADCLEARANCE3fd1c3eec8fbad8c, benchMode=null, userContextInfo=null, deviceDeliveryCutoff=1745736014867, duplicateMessage=null, ecuType=null, mqttTopic=null, platformId=ssdp-connected, eventId=RoadClearanceMetadataResponse, version=1.0, timestamp=1745735834867, eventData=RoadClearanceMetadataResponseV1_0{data=RoadClearanceMetadataResponseData{catalogVersion=9, catalogTimestamp=1742947931807, tileMetadataList=[]}, responseCode='RC_SUCCESS', failedTileList=FailedTileList{failedTileIds=[]}, noEventTileList=NoEventTileList{noEventTileIds=[121212132]}}, requestId=null, sourceDeviceId=null, vehicleId=T0000000000000150, kafkaHeaders=null], getClass()=class com.harman.ignite.entities.IgniteEventImpl, hashCode()=130088150] by worker:DffAgentPostProecssor

2. But Retry record still created with key 0_2:T0000000000000150;600001, this key(T0000000000000150) is VehicleID
DEBUG-Created event RetryRecord [igniteKey=IgniteStringKey [key=T00000000000150], deviceMessage=DeviceMessage [message=[8, -13, -71, -37, -81, -25, 50, 18, 31, 65, 68, 82, 79, 65, 68, 67, 76, 69, 65, 82, 65, 78, 67, 69, 51, 102, 100, 49, 99, 51, 101, 101, 99, 56, 102, 98, 97, 100, 56, 99, 24, -63, -49, 36, 32, 31, 42, 23, -38, -53, 1, 19, 10, 9, 8, 9, 16, -97, -83, -85, -2, -36, 50, 34, 6, 10, 4, -28, -103, -26, 57], version=1.0, deviceMessageHeader=DeviceMessageHeader [messageId=600001, correlationId=31, requestId=null, vehicleId=T0000000000000150, platformId=ssdp-connected, targetDeviceId=T00000000000150, deviceRoutable=true, responseExpected=true, shoulderTapEnabled=false, deviceDeliveryCutoff=1745736014867, timestamp=1745735834867, timezone=0, devMsgTopicSuffix=null, devMsgTopicPrefix=null, devMsgGlobalTopic=null], retryInterval= 40000 ], attempts=0, lastRetryTimestamp=1745735834889, version=null, extraParameters=null] with key 0_2:T0000000000000150;600001 to retry event map.

3. Event published to MQTT broker
4.V2C  Acknowledgement event received with key as deviceID i.e., T00000000000150
06:38:38.871 [road-clearance-sp-ca0b9a99-b453-4c63-887d-aca8af55d46d-StreamThread-1] DEBUG-IgniteEvent after transformation IgniteEventImpl [getNestedEvents()=[], getEventId()=Acknowledgement, getVersion()=1.0, getTimestamp()=1745735917794, getEventData()=AcknowledgementV1_0 [status=SUCCESS], getRequestId()=null, getSourceDeviceId()=T00000000000150, getVehicleId()=null, getSchemaVersion()=1.0, getDFFQualifier()=null, getTargetDeviceId()=Optional.empty, getMessageId()=34, getCorrelationId()=600001, getBizTransactionId()=ADROADCLEARANCE3fd1c3eec8fbad8c, isDeviceRoutable()=false, toString()=AbstractIgniteEvent [timezone=0, dffQualifier=null, targetDeviceId=null, messageId=34, correlationId=600001, bizTransactionId=ADROADCLEARANCE3fd1c3eec8fbad8c, benchMode=null, userContextInfo=null, deviceDeliveryCutoff=-1, duplicateMessage=null, ecuType=null, mqttTopic=null, platformId=null, eventId=Acknowledgement, version=1.0, timestamp=1745735917794, eventData=AcknowledgementV1_0 [status=SUCCESS], requestId=null, sourceDeviceId=T00000000000150, vehicleId=null, kafkaHeaders=null], getClass()=class com.harman.ignite.entities.IgniteEventImpl, hashCode()=6435829] for key IgniteStringKey [key=T00000000000150]

5. And attempted to delete retry record with key 0_0:T00000000000150; 600001 , this key(T00000000000150) is DeviceID

06:38:02.147 [road-clearance-sp-ca0b9a99-b453-4c63-887d-aca8af55d46d-StreamThread-1: CacheBypassThread:0_14] DEBUG-DeleteMapOfEntities operation complete for key 0_0:T00000000000150;600001 and value null

Code of Conduct

• I agree to follow this project's Code of Conduct

[kaushalaroraharman]

As I can observe, the retry record is still being created with vehicleID, as opposed to the key in the C2V event which is deviceID. This a bug in stream-base code which needs a code change to be fixed, and we will pick it up in the next release. Please note, we are currently in the middle of open-source migration work, and it will take some time before we can fix this and provide you with a release. In the meantime, if possible, as a workaround on your side, you can use the key as Vehicle ID for both the C2V event, as well as the acknowledgement events.

Also, I still see the partition number on which RoadClearanceMetadataResponse is being processed is 2 (from task ID 0_2), and that for acknowledgement is 0 (from task ID 0_0), since key is deviceID for both, it suggests they are coming on different topics. Please ensure that both the source event and the acknowledgement are received either on the same topic, or topics with same number of partitions.