You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Jagadish (JIRA)" <ji...@apache.org> on 2016/03/17 21:26:33 UTC
[jira] [Updated] (SAMZA-901) SamzaAppState re-design and bug fixes
[ https://issues.apache.org/jira/browse/SAMZA-901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jagadish updated SAMZA-901:
---------------------------
Description:
There are a bunch of state data structures that are publicly exposed in SamzaAppState. These must be made thread-safe into accessors. These public global variables could mutated everywhere in Samza without regard for safety/visibility or correctness.
Making the SamzaAppState thread-safe will fix these potential races in code. Also, as Samza evolves, it is useful to provide accessors instead of exposing all the public variables.
was:
There are a bunch of state data structures that are publicly exposed in SamzaAppState. These must be made thread-safe into accessors. These public global variables could mutated everywhere in Samza without regard for safety/visibility or correctness.
Making the SamzaAppState thread-safe will fix these races in code.
For example, there is an integer containerCount that is public which is manipulated by both the metrics reporter and the callback threads.
> SamzaAppState re-design and bug fixes
> -------------------------------------
>
> Key: SAMZA-901
> URL: https://issues.apache.org/jira/browse/SAMZA-901
> Project: Samza
> Issue Type: Bug
> Reporter: Jagadish
>
> There are a bunch of state data structures that are publicly exposed in SamzaAppState. These must be made thread-safe into accessors. These public global variables could mutated everywhere in Samza without regard for safety/visibility or correctness.
> Making the SamzaAppState thread-safe will fix these potential races in code. Also, as Samza evolves, it is useful to provide accessors instead of exposing all the public variables.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)