Hi
First of all my apologies for voting late. However, I will still do it
since the mail says the vote would remain open for *at least* 72 hours :)
I believe the objective is to do the right things rightly.
Moving to a new version is something that is a part of any product
lifecycle. While doing
rtly.
> >
> > I will propose let's keep this open for sometime and we focus on
> > identifying changes which should go in next major version and then go for
> > it.
> >
> > -1 for immediate release or even making release branch now.
> >
> > -Priyanka
+1
On Thu, Oct 27, 2016 at 11:21 AM, Chinmay Kolhatkar
wrote:
> +1.
>
> On Thu, Oct 27, 2016 at 1:41 AM, Thomas Weise wrote:
>
> > Hi,
> >
> > I'm proposing another release of Malhar in November. There are 49 issues
> > marked for the release, including important bug fixes, new documentation,
>
We have seen 2 cases mentioned below, where, it would have been nice if
Apex allowed us to exclude a node from the cluster for an application.
1. A node in the cluster had gone bad (was randomly rebooting) and so an
Apex app should not use it - other apps can use it as they were batch jobs.
2. A n
While it is possible to extend anti-affinity to take care of this, I feel
it will cause confusion from a user perspective. As a user, when I think
about anti-affinity, what comes to mind right away is a relative relation
between operators.
On the other hand, the current ask is not that, but a rela
My previous mail explains it, but just forgot to add : -1 to cover this
under anti affinity.
On Fri, Dec 2, 2016 at 12:46 PM, Milind Barve wrote:
> While it is possible to extend anti-affinity to take care of this, I feel
> it will cause confusion from a user perspective. As a user,
Additionally, this would apply to Stram as well i.e. the master should also
not be deployed on these nodes. Not sure if anti-affinity goes beyond
operators.
On Fri, Dec 2, 2016 at 12:47 PM, Milind Barve wrote:
> My previous mail explains it, but just forgot to add : -1 to cover this
>
Dec 1, 2016 at 11:52 PM Amol Kekre wrote:
>
> > Yarn will deploy AM (Stram) on a node of its choice, therey rendering any
> > attribute within the app un-enforceable in terms of not deploying master
> on
> > a node.
> >
> > Thks
> > Amol
> >
> >
&g
[
https://issues.apache.org/jira/browse/APEXCORE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15714319#comment-15714319
]
Milind Barve commented on APEXCORE-584:
---
Please note that this is a