+1
On Tue, May 15, 2018 at 10:56 AM, Billie Rinaldi
wrote:
> Since there has been no additional activity on the discussion thread, it is
> time to call vote. Please vote on whether we should retire the Slider
> podling. Here is my +1.
>
> [ ] +1 Retire Slider
> [ ] +0
+1
On Wed, May 2, 2018 at 1:13 PM, Gour Saha wrote:
> +1
>
> -Gour
>
> > On May 2, 2018, at 9:12 AM, Ted Yu wrote:
> >
> > +1
> >
> > On Wed, May 2, 2018 at 8:27 AM, Billie Rinaldi >
> > wrote:
> >
> >> Hi all, here is a
figPublishingIT
>
> Results :
>
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
>
>
> -Gour
>
> On 3/13/17, 8:38 AM, "Billie Rinaldi" <billie.rina...@gmail.com> wrote:
>
> >I haven't run the functional suite myself for this RC. I seem to recall
&
:43,424 [AmExecutor-006] INFO state.RoleHistory
(RoleHistory.java:findRecentNodeForNewInstance(625)) - No node found for
COMMAND_LOGGER
On Sun, Mar 12, 2017 at 6:17 PM, jonma...@gmail.com <jonma...@gmail.com>
wrote:
> Anyone else attempted running the functional suite? I'm getting some
Anyone else attempted running the functional suite? I'm getting some
errors against an HDP 2.4 cluster (2.4.2.0-258):
Failed tests:
Should it actually be "APPNAME" instead of "APPNMAE"?
On Thu, Mar 2, 2017 at 11:29 PM, David.Serafini
wrote:
> when I run : slider diagnostics --application --name
>
> "global" : {
> "site.global.port" : "${APPNMAE.ALLOCATED_PORT}{PER_CONTAINER}",
>
>
> How do
Can you provide your app config file? Perhaps the combination of
properties you've specified is triggering an attempt to connect securely?
Are you specifiying the client properties in slider-client.xml or pointint
to the hadoop conf directory? If the latter, are you certain that hadoop
My guess is there's actually a need to have the MapR hadoop common jar (the
one I would assume has an updated file system implementation) be pre-pended
to the class path. I don't have an installation in front of me, but I'd
look into modifying slider-env or the like to prepend at least that one
+1 - this approach definitely addresses an important need.
The project has gone through at least a couple of development/repo
approaches:
1) git-flow with master/develop branches
2) abandonment of the master branch and work/releases based on the develop
branch.
I have no strong objections to