apache flink - Ensuring local caching with Ignite on YARN -


i have stream processing application written in flink & want use internal key-value store state backend compute streaming aggregates. because dealing lot of aggregates, avoid maintaining them on-heap inside flink application memory-backed , file-backed implementations offer. in stead, maintain cache of state in apache ignite, in turn use write-through & read-through features provide more reliable back-up in hbase.

ideally, have single local ignite cache on every physical node handles state long-running flink operators on node. e.g. each node has single ignite node in 8 gb container available, whether running 1 or 10 flink operators.

the problem want both flink , ignite run on yarn. through consistent partitioning, can ensure data in general sent correct cache, , in case of failures etc., can refilled hbase. problem i'm facing though ignite seems request containers yarn randomly, meaning have no guarantee there in fact local cache available, if set amount of ignite nodes same amount of physical nodes.

any suggestions on how achieve 1 ignite node per physical node set up?

there ticket created enhance resource allocation using yarn: https://issues.apache.org/jira/browse/ignite-3214. in community puck , fix.


Comments

Popular posts from this blog

javascript - jQuery: Add class depending on URL in the best way -

caching - How to check if a url path exists in the service worker cache -

Redirect to a HTTPS version using .htaccess -