[
https://issues.apache.org/jira/browse/SAMZA-411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Naveen updated SAMZA-411:
-------------------------
Description: The current Samza job settings require we need to specify both
the container configuration and the java memory opts. It would be easier to use
to the job just had to specify only one memory configuration and we infer the
container and JMX memory settings from it. It gets a little more interesting
when have state management, because the state management itself needs some
memory - which could live outside of JVM (like LevelDB/RocksDB..) (was: The
current Samza job settings require we need to specify both the container
configuration and the java memory opts. It would be easier to use to the job
just had to specify only one memory configuration and we infer the container
and JMX memory settings from it. It gets a little more interesting when have
state management, because the state management itself needs some memory- which
could live outside of JVM (like LevelDB/RocksDB..))
> Unify memory configuration
> ---------------------------
>
> Key: SAMZA-411
> URL: https://issues.apache.org/jira/browse/SAMZA-411
> Project: Samza
> Issue Type: Improvement
> Components: container
> Reporter: Naveen
> Priority: Minor
>
> The current Samza job settings require we need to specify both the container
> configuration and the java memory opts. It would be easier to use to the job
> just had to specify only one memory configuration and we infer the container
> and JMX memory settings from it. It gets a little more interesting when have
> state management, because the state management itself needs some memory -
> which could live outside of JVM (like LevelDB/RocksDB..)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
