clear query| facets| time Search criteria: .   Results from 1 to 3 from 3 (0.0s).
Loading phrases to help you
refine your search...
[SAMZA-1746] Coordinator stuck connecting to a decommissioned NM - Samza - [issue]
...We hit an issue trying to decommission a large number of NMs. We've decommissioned large number of NMs Containers were allocated by RM to a new NM That NM was decommissioned immediately afte...
http://issues.apache.org/jira/browse/SAMZA-1746    Author: Danil Serdyuchenko , 2018-06-12, 09:53
[SAMZA-1116] Yarn RM recovery causing duplicate containers - Samza - [issue]
...To replicate: Make sure that Yarn RM recovery is enabled Deploy a test job Terminate Yarn RM Wait until AM of the job terminate with:2017-02-02 13:08:04 RetryInvocationHandler [WARN] Excepti...
http://issues.apache.org/jira/browse/SAMZA-1116    Author: Danil Serdyuchenko , 2017-12-20, 21:38
[SAMZA-983] A separate setting for AM vcpu count - Samza - [issue]
...We hit an issue mentioned in: SAMZA-783 after we enabled hard cpu isolation on our yarn cluster. From our analysis we could see a few compounding reasons for the outage: A samza job with a l...
http://issues.apache.org/jira/browse/SAMZA-983    Author: Danil Serdyuchenko , 2016-07-29, 13:17