gt; >> > > But
>> >> > > > that's something worth exploring.
>> >> > > >
>> >> > > > Thanks,
>> >> > > > Santosh
>> >>
gt; > > > wrote:
> >> > > >
> >> > > >> On MYRIAD-160, it's a really bad idea to let Myriad pick a random
> >> port
> >> > > >> outside of Mesos as other frameworks might select that port the
> >> > &g
gt;> probability
>> > > >> of that happening is 1-(number of ports requested by other
>> > > >> frameworks)/(number of ports in use). This could get near 50% and
>> > cause
>> > > >> frameworks that are being good citizens to crash.
> frameworks)/(number of ports in use). This could get near 50% and
> > cause
> > > >> frameworks that are being good citizens to crash.
> > > >>
> > > >> I'm also not convinced randomizing the port is in fact the correct
> f
> > for
> > >> this in the long term, as there is still a non-zero chance you'll get
> > that
> > >> port again.
> > >>
> > >> Darin
> > >>
> > >>
> > >>
> > >> On Fri, Oct 23, 2015 at 12:56 AM,
> >> port again.
> >>
> >> Darin
> >>
> >>
> >>
> >> On Fri, Oct 23, 2015 at 12:56 AM, yuliya Feldman <
> >> yufeld...@yahoo.com.invalid> wrote:
> >>
> >> > Great list.
> >> > I would in
feld...@yahoo.com.invalid> wrote:
>>
>> > Great list.
>> > I would include MYRIAD-160 to the list - I am working on that one. Of
>> > course as a workaround we could not use Mesos ports and let NM ports
>> > randomization kick in.I also almost done with MYRIA
hould submit PR tonight.
> > Thanks,Yuliya
> > From: Darin Johnson
> > To: Dev
> > Sent: Thursday, October 22, 2015 8:29 PM
> > Subject: Re: JIRA work for 0.1.0
> >
> > I think this sounds good about right. A few Jim marked were new
> features,
s much lower chance then consistently getting the same port w/o
> randomization.
> Thanks,Yuliya From: Darin Johnson
> To: Dev ; yuliya Feldman <
> yufeld...@yahoo.com>
> Sent: Friday, October 23, 2015 9:57 AM
> Subject: Re: JIRA work for 0.1.0
>
> On MYRIAD
Subject: Re: JIRA work for 0.1.0
On MYRIAD-160, it's a really bad idea to let Myriad pick a random port
outside of Mesos as other frameworks might select that port the probability
of that happening is 1-(number of ports requested by other
frameworks)/(number of ports in use). This could get
hat one. Of
> > course as a workaround we could not use Mesos ports and let NM ports
> > randomization kick in.I also almost done with MYRIAD-148 - it was really
> > tricky. Should submit PR tonight.
> > Thanks,Yuliya
> > From: Darin Johnson >
> > To: Dev >
&g
> Thanks,Yuliya
> From: Darin Johnson
> To: Dev
> Sent: Thursday, October 22, 2015 8:29 PM
> Subject: Re: JIRA work for 0.1.0
>
> I think this sounds good about right. A few Jim marked were new features,
> gotta leave something for the 0.2.0 release :).
>
&g
Johnson
To: Dev
Sent: Thursday, October 22, 2015 8:29 PM
Subject: Re: JIRA work for 0.1.0
I think this sounds good about right. A few Jim marked were new features,
gotta leave something for the 0.2.0 release :).
On Thu, Oct 22, 2015 at 8:08 AM, Santosh Marella
wrote:
> I looked at
I think this sounds good about right. A few Jim marked were new features,
gotta leave something for the 0.2.0 release :).
On Thu, Oct 22, 2015 at 8:08 AM, Santosh Marella
wrote:
> I looked at the JIRAs currently marked with fix version "myriad-0.1.0".
> There were 19 of them. I moved a few out
> just didn't want things to be missed..
Jim.. great thinking! Let me know if you see a JIRA that should be in the
show stopper list.
And.. thanks for being an amazing volunteer on the project!
Regards,
Santosh
On Thu, Oct 22, 2015 at 5:27 AM, Jim Klucar wrote:
> Sounds good. I wasn't trying t
Sounds good. I wasn't trying to usurp Santosh at all, just didn't want
things to be missed and I saw some easy ones out there. Just so you know,
even though my vote isn't a binding one, I plan on deploying the release
and testing it.
Jim
On Thu, Oct 22, 2015 at 8:08 AM, Santosh Marella
wrote:
>
I looked at the JIRAs currently marked with fix version "myriad-0.1.0".
There were 19 of them. I moved a few out. We are currently at 14.
However, IMO the show stoppers are really the following:
MYRIAD-43 Replace com.ebay namespace with org.apache
MYRIAD-44 Prepare for 0.1.0 release
MYRIAD-98 Mov
Keep in mind that Santosh (as Release Manager) has final authority over
pushing things out of 0.1.0.
I created a (hopefully public) filter for Unresolved 0.1.0 Myriad JIRAs:
https://issues.apache.org/jira/browse/MYRIAD-44?filter=12333786
Maybe we should create a dashboard too, like
https://issues
I went through JIRA and assigned a bunch of the tickets to the Myriad 0.1.0
release. Some of them are really low hanging fruit, so I think we can knock
most of these out. As Adam said in the meeting, we'd rather have too many
flagged for the release and pair down rather than miss some. To that end,
19 matches
Mail list logo
