ne so far
> > From: John Omernik
> > To: dev@myriad.incubator.apache.org; yuliya Feldman <
> yufeld...@yahoo.com>
> > Sent: Tuesday, August 18, 2015 1:44 PM
> > Subject: Re: Myriad 0.1 release scope
> >
> > (So if I clone that repo, am I clon
3:48 PM, yuliya Feldman wrote:
> mesos/myriad is the right one so far
> From: John Omernik
> To: dev@myriad.incubator.apache.org; yuliya Feldman
> Sent: Tuesday, August 18, 2015 1:44 PM
> Subject: Re: Myriad 0.1 release scope
>
> (So if I clone that repo, am I cloning
mesos/myriad is the right one so far
From: John Omernik
To: dev@myriad.incubator.apache.org; yuliya Feldman
Sent: Tuesday, August 18, 2015 1:44 PM
Subject: Re: Myriad 0.1 release scope
(So if I clone that repo, am I cloning the right one?)
On Tue, Aug 18, 2015 at 3:43 PM, John
ubator.apache.org
>> Sent: Tuesday, August 18, 2015 1:35 PM
>> Subject: Re: Myriad 0.1 release scope
>>
>> On the release scope, will having the myriad configuration file exist
>> outside the jar (i.e. you can change configuration without rebuilding) be
>> part
sspath: like .../etc/hadoop
> From: John Omernik
> To: dev@myriad.incubator.apache.org
> Sent: Tuesday, August 18, 2015 1:35 PM
> Subject: Re: Myriad 0.1 release scope
>
> On the release scope, will having the myriad configuration file exist
> outside the jar (i.e. y
You actually do not need to rebuild even today - just keep this file in hadoop
config directory that is on the classpath: like .../etc/hadoop
From: John Omernik
To: dev@myriad.incubator.apache.org
Sent: Tuesday, August 18, 2015 1:35 PM
Subject: Re: Myriad 0.1 release scope
On the
On the release scope, will having the myriad configuration file exist
outside the jar (i.e. you can change configuration without rebuilding) be
part of the .1 release scope?
On Mon, Aug 10, 2015 at 10:01 PM, Santosh Marella
wrote:
> Hello All,
>
> I've merged the FGS changes into phase1. Built
Hello All,
I've merged the FGS changes into phase1. Built and tested both coarse
grained scaling and fine grained scaling, UI on a 4 node cluster.
If anyone finds things are not working as expected, please let me know.
Thanks,
Santosh
On Fri, Aug 7, 2015 at 10:46 AM, Santosh Marella
wrote:
Not sure it's that simple. I think this requires reflection based API
invocation based on hadoop version. Also the hadoop version itself needs to
be passed from build file into Java code.
Hadoop eco system components like Hive adopt a technique called shim
loaders to solve this type of problems.
So I compiled the 2.5 fgs against 2.6 when I was testing. If we abstract
this right it may just be an if statement or two.
On Aug 7, 2015 6:47 PM, "Santosh Marella" wrote:
> > Myriad code base compiled against hadoop 2.7 should work on hadoop 2.5
> > cluster as long as FGS (i.e. zero profile NM)
> Myriad code base compiled against hadoop 2.7 should work on hadoop 2.5
> cluster as long as FGS (i.e. zero profile NM) is not used.
Verified the above. As long as FGS (zero profile NM) is not used,
Myriad compiled against hadoop 2.7 will work on hadoop 2.5.
Thanks,
Santosh
On Fri, Aug 7, 2015
> It will make working on HA easier
Oh Yes!
> how do we facilitate that? Profiles?
Profiles might be one way. Currently, FGS is supported for "zero" profile
only.
And we have seen there was an API incompatibility from 2.5 to 2.6+ in FGS
code.
So, ideally (since I haven't tried it myself), when FGS
It will make working on HA easier. However, one concern that's been
addressed previously is that FGS works for Hadoop 2.6.0+. Do we plan to
support 2.5.X (anything lower?) also as Santosh has a way to do that, if so
how do we facilitate that? Profiles?
Darin
On Fri, Aug 7, 2015 at 1:46 PM, Santo
Hello guys,
I propose merging FGS into phase1. As I said before, I think it's at a
point where the functionality works reasonably well.
Any future improvements/fixes/UI changes can be done via separate JIRAs.
Unless there are any major concerns, I'd like to merge FGS into phase1 *EOD
Monday* (PDT
ot make it to
> the
> > > mailing list.
> > > resending...
> > >
> > > Regards
> > > Swapnil
> > >
> > >
> > > -- Forwarded message --
> > > From: Swapnil Daingade
> > > Date: Thu, Aug 6, 2015 at 12:0
@gmail.com
> > wrote:
>
> > Just learned from Santosh that my email last night did not make it to the
> > mailing list.
> > resending...
> >
> > Regards
> > Swapnil
> >
> >
> > -- Forwarded message --
> > From: Swapnil D
--
> From: Swapnil Daingade
> Date: Thu, Aug 6, 2015 at 12:00 AM
> Subject: Re: Myriad 0.1 release scope
> To: dev@myriad.incubator.apache.org
>
>
>
> I think Myriad HA is also in good shape. We discussed work preserving NM
> restart internally and it looks like i
Just learned from Santosh that my email last night did not make it to the
mailing list.
resending...
Regards
Swapnil
-- Forwarded message --
From: Swapnil Daingade
Date: Thu, Aug 6, 2015 at 12:00 AM
Subject: Re: Myriad 0.1 release scope
To: dev@myriad.incubator.apache.org
I
I feel FGS is very close to making it into 0.1. PR 116 addresses moving to
hadoop 2.7 and making FGS and CGS coexist. This PR was recently reviewed by
Yulia and Darin. Darin had also tried out FGS on hadoop 2.6.x and 2.7.x
clusters and it seemed to have worked as expected. Unless there are more
rev
We do have a JIRA 0.1.0 "fix version" field, but none of our issues use it
yet.
I think the goal was just to take what we have and make it work under
Apache infrastructure, then vote on that for 0.1.0.
Although other features like HA or FGS would be great, let's try to get our
first Apache release
Hi all,
Was wondering what would be the scope for the Myriad 0.1 release.
It would be nice to have a roadmap page somewhere and target
features to releases (JIRA 'fix version' field perhaps)
Regards
Swapnil
21 matches
Mail list logo
