I’ve run into this same issue with a BatchJob I’ve implemented. I’ve tried increasing the NormalizationMaxLockAttempts to 1000 but still occasionally get the error. After increasing the attempts I also started getting the following error:
errorMsg: c3.love.exceptions.C3RuntimeException: c3.love.exceptions.C3RuntimeException: MetricEngine error : c3.love.exceptions.C3RuntimeException: Error c3.love.exceptions.C3RuntimeException: Unable to normalize timeseries action=fetchNormalizedData,type=RollupHistoricalTestSeries,parentId=PC|F|0000002230|1319,error=Internal Error : Could not resolve concurrency scenario for normalization after 3 attempts. at c3.engine.database.timeseries.normn.FetchNormalizedDataTask.throwError(FetchNormalizedDataTask.java:191) at ...
Both errors show up in BatchQueue.errors().
Each batch of my batch job runs a rollupMetrics() function. There is a very rare chance that there could be a timeseries ID in common, among two sets of IDs that are running on two different batches at once.
Could that be what is causing these errors? Any ideas? Thanks in advance!