OK. If I understand correctly, your answer is the following:
yarn.resources.* configuration variables are used by YARN localizer to make
API and infrastructure classpath available, together with the application's
own classpath, which is also determined by the YARN localizer.
The question here is:
The configuration variables are only used by the YARN localizer. The Samza
application will look for the framework resources in certain places in the
application's working directory when it needs to access them. My aim is to
do something similar to how "yarn.package.path" works. In other execution
The vote has passed. Thanks!
+1 (binding) x 3: Yi, Xinyu, Bharath
Cameron
On Wed, Mar 11, 2020 at 3:28 PM Bharath Kumara Subramanian <
codin.mart...@gmail.com> wrote:
> +1(binding).
>
> Check-all.sh and the integration tests passed.
>
> Thanks,
> Bharath
>
> On Tue, Mar 10, 2020 at 3:35 PM
Hi, Jeremiah,
Sorry to reply late. This WARN message indicates that producer failed to
flush to checkpoint topic and would retry. Do you see the Samza job hanging
after that? Is the checkpointed offset metrics incrementing in this case?
Not clear on your claiming: "logs stop at that point". No
Hi, Cameron,
Thanks for the quick responses! Appreciate it.
I am still having a concern on a): are those configuration variables used
by YARN localizer or by Samza applications? If those are used only by the
YARN localizer, I agree that we should keep those as yarn specific.
Otherwise, I think
+1(binding).
Check-all.sh and the integration tests passed.
Thanks,
Bharath
On Tue, Mar 10, 2020 at 3:35 PM Xinyu Liu wrote:
> +1 (binding).
>
> Run check-all.sh and integration tests for both yarn and standalone. All
> passed.
>
> Thanks,
> Xinyu
>
>
> On Fri, Mar 6, 2020 at 6:46 PM Yi Pan
Can anyone take a look at the message below? We are trying to gauge our risk
before moving forward.
Jeremiah Adams
Software Engineer
www.helixeducation.com
Blog | Twitter | Facebook | LinkedIn
From: Jeremiah Adams
Sent: Wednesday, March 4, 2020 2:28 PM
