Hunter Moffitt created SAMZA-2794:
-------------------------------------
Summary: SSPGrouperProxy Partition Count Change Error
Key: SAMZA-2794
URL: https://issues.apache.org/jira/browse/SAMZA-2794
Project: Samza
Issue Type: Bug
Reporter: Hunter Moffitt
When Standby Partitions are disabled and the Job is redeployed, a new set of
coordinator stream messages are written for the "set-task-partition-assignment"
namespace without the standby partitions listed in them. The messages include
the new addition to the key from Samza elasticity changes \"keyBucket\":-1}".
Because of the addition to the key, both the prior partition assignments and
the new partition assignments are read as separate entries. Depending on the
order the entries processed, the mapping is overwritten when the second
processed entry for the same SystemStreamPartition is processed, resulting in
inconsistent mappings with some of the SystemStreamPartitions containing
Standby partition tasknames and others only containing the current Partitions
as tasknames. In JobModelHelper, where the the standby partitions would be
filtered out by comparing against the taskMode mapping, the taskMode mapping
does not contain information about any standby partitions, so they fall under
the default case of !taskModes.containsKey(taskName) and move on to the
GrouperMetaData, and then are counted by the SSPGrouperProxy.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
