[
https://issues.apache.org/jira/browse/BEAM-12229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17332835#comment-17332835
]
Steve Niemitz commented on BEAM-12229:
--------------------------------------
So perhaps even more concerning, looking at my application level metrics for
the time period I had beam deployed with 2.29, I see some very suspicious
looking numbers. Particularly, our persisted accumulator (ie, combiner state)
size was much smaller in beam 2.29 than previously, and went back to normal
when I reverted that commit. This should be unaffected by anything internal to
beam (or cache for that matter), so I'm kind of concerned we were actually
seeing some form of data loss here. I'm going to try to compare data between
the two to see if there actually are discrepancies.
> WindmillStateCache has a 0% hit rate in 2.29
> --------------------------------------------
>
> Key: BEAM-12229
> URL: https://issues.apache.org/jira/browse/BEAM-12229
> Project: Beam
> Issue Type: Bug
> Components: runner-dataflow
> Affects Versions: 2.29.0
> Reporter: Steve Niemitz
> Assignee: Reuven Lax
> Priority: P1
>
> After upgrading to 2.29, I noticed that our jobs have a 0% state cache hit
> rate. I see a very high eviction rate from the cache as well (it used to be
> ~0, now its ~100,000+ evictions / second).
> We never were on 2.28, so I can't say if it worked there, but it did work on
> 2.27.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
