[
https://issues.apache.org/jira/browse/SLIDER-742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14270310#comment-14270310
]
Yang Hao edited comment on SLIDER-742 at 1/9/15 6:21 AM:
-
>From th
The "slider registry" command should provide you a way to access formatted
configs and exports.
E.g.
slider registry --name cl1 --getexp servers
2015-01-09 01:41:42,466 [main] INFO impl.TimelineClientImpl - Timeline
service address: http://c6403.ambari.apache.org:8188/ws/v1/timeline/
2015-01-09
[
https://issues.apache.org/jira/browse/SLIDER-723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated SLIDER-723:
-
Sprint: Slider Jan #1
> Memcached component launch fail does not propagate
> -
[
https://issues.apache.org/jira/browse/SLIDER-723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated SLIDER-723:
-
Assignee: Sumit Mohanty
> Memcached component launch fail does not propagate
> ---
[
https://issues.apache.org/jira/browse/SLIDER-723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14270334#comment-14270334
]
Sumit Mohanty commented on SLIDER-723:
--
Reproduced the scenario:
* Container fails at
[
https://issues.apache.org/jira/browse/SLIDER-726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated SLIDER-726:
-
Summary: Different instances of the same component should run on different
nodes (anti-affinity)
[
https://issues.apache.org/jira/browse/SLIDER-742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14270310#comment-14270310
]
Yang Hao commented on SLIDER-742:
-
>From this point of view, it should have keytab file
>
[
https://issues.apache.org/jira/browse/SLIDER-737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yang Hao updated SLIDER-737:
Comment: was deleted
(was: Do you mean adding this when executing the slider client command?
It is to be ve
[
https://issues.apache.org/jira/browse/SLIDER-566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty resolved SLIDER-566.
--
Resolution: Not a Problem
Apps are free to add ACL to sub-nodes created under the default path.
[
https://issues.apache.org/jira/browse/SLIDER-688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated SLIDER-688:
-
Sprint: Slider Jan #1
> Zero touch install support
> --
>
>
[
https://issues.apache.org/jira/browse/SLIDER-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty resolved SLIDER-398.
--
Resolution: Fixed
We can resolve this as 0.60 had the fix as well (I forgot to cherry-pick and
[
https://issues.apache.org/jira/browse/SLIDER-737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yang Hao updated SLIDER-737:
Comment: was deleted
(was: Do you mean adding this when executing the slider client command?
It is to be ve
[
https://issues.apache.org/jira/browse/SLIDER-737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yang Hao updated SLIDER-737:
Comment: was deleted
(was: Do you mean adding this when executing the slider client command?
It is to be ve
[
https://issues.apache.org/jira/browse/SLIDER-737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yang Hao updated SLIDER-737:
Comment: was deleted
(was: Do you mean adding this when executing the slider client command?
It is to be ve
[
https://issues.apache.org/jira/browse/SLIDER-737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14270293#comment-14270293
]
Yang Hao commented on SLIDER-737:
-
Do you mean adding this when executing the slider clie
[
https://issues.apache.org/jira/browse/SLIDER-737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yang Hao updated SLIDER-737:
Comment: was deleted
(was: Do you mean adding this when executing the slider client command?
It is to be ve
[
https://issues.apache.org/jira/browse/SLIDER-737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yang Hao updated SLIDER-737:
Comment: was deleted
(was: Do you mean adding this when executing the slider client command?
It is to be ve
[
https://issues.apache.org/jira/browse/SLIDER-737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14270287#comment-14270287
]
Yang Hao commented on SLIDER-737:
-
Do you mean adding this when executing the slider clien
[
https://issues.apache.org/jira/browse/SLIDER-737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14270291#comment-14270291
]
Yang Hao commented on SLIDER-737:
-
Do you mean adding this when executing the slider clien
[
https://issues.apache.org/jira/browse/SLIDER-737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14270289#comment-14270289
]
Yang Hao commented on SLIDER-737:
-
Do you mean adding this when executing the slider clien
[
https://issues.apache.org/jira/browse/SLIDER-737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14270288#comment-14270288
]
Yang Hao commented on SLIDER-737:
-
Do you mean adding this when executing the slider clien
[
https://issues.apache.org/jira/browse/SLIDER-737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14270290#comment-14270290
]
Yang Hao commented on SLIDER-737:
-
Do you mean adding this when executing the slider clien
[
https://issues.apache.org/jira/browse/SLIDER-737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14270292#comment-14270292
]
Yang Hao commented on SLIDER-737:
-
Do you mean adding this when executing the slider clien
On Jan 8, 2015, at 1:58 PM, Steve Loughran wrote:
> On 8 January 2015 at 18:15, Nitin Aggarwal
> wrote:
>
>> +1. Also, should the node with failure threshold reached, be ever
>> considered in future for allocation ?
>> It is possible that due to some temporary issues with few nodes, locality
>
+1
On Jan 8, 2015, at 2:13 PM, Sumit Mohanty wrote:
> Sounds good. +1
>
> On Thu, Jan 8, 2015 at 11:03 AM, Steve Loughran
> wrote:
>
>> The Apache Ambari need maven-central hosted Slider artifacts, which means
>> that we need to release some.
>>
>> I'm hoping just to backport the maven build
Sounds good. +1
On Thu, Jan 8, 2015 at 11:03 AM, Steve Loughran
wrote:
> The Apache Ambari need maven-central hosted Slider artifacts, which means
> that we need to release some.
>
> I'm hoping just to backport the maven build changes needed to enable this
> onto the 0.6x branch, so that we can
The Apache Ambari need maven-central hosted Slider artifacts, which means
that we need to release some.
I'm hoping just to backport the maven build changes needed to enable this
onto the 0.6x branch, so that we can give them which matches what they've
been building against, slider-0.60.
We can th
On 8 January 2015 at 18:15, Nitin Aggarwal
wrote:
> +1. Also, should the node with failure threshold reached, be ever
> considered in future for allocation ?
> It is possible that due to some temporary issues with few nodes, locality
> node set, could have a lot more nodes than needed.
>
There's
+1. Also, should the node with failure threshold reached, be ever
considered in future for allocation ?
It is possible that due to some temporary issues with few nodes, locality
node set, could have a lot more nodes than needed.
On Thu, Jan 8, 2015 at 9:19 AM, Steve Loughran
wrote:
> https://iss
https://issues.apache.org/jira/browse/SLIDER-743 it is then.
On 8 January 2015 at 14:26, Jon Maron wrote:
> +1. A good way to provide the functionality while leveraging existing
> mechanisms
>
> On Jan 8, 2015, at 8:46 AM, Gour Saha wrote:
>
> > +1 on that
> >
> > That's also what I meant when
[
https://issues.apache.org/jira/browse/SLIDER-737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14269690#comment-14269690
]
Steve Loughran commented on SLIDER-737:
---
seems reasonable.
Would it be possible/cle
[
https://issues.apache.org/jira/browse/SLIDER-710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran resolved SLIDER-710.
---
Resolution: Fixed
> Restore insecure WS "back door" for REST dev
> ---
Steve Loughran created SLIDER-743:
-
Summary: Include node failure history when choosing placement hints
Key: SLIDER-743
URL: https://issues.apache.org/jira/browse/SLIDER-743
Project: Slider
I
[
https://issues.apache.org/jira/browse/SLIDER-742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14269361#comment-14269361
]
Jonathan Maron commented on SLIDER-742:
---
I think you may be confusing some concepts.
+1. A good way to provide the functionality while leveraging existing
mechanisms
On Jan 8, 2015, at 8:46 AM, Gour Saha wrote:
> +1 on that
>
> That's also what I meant when I said -
>>> I don't think we have a logic where we apply data locality and then upon a
>>> certain no of failures (thr
+1 on that
That's also what I meant when I said -
>> I don't think we have a logic where we apply data locality and then upon a
>> certain no of failures (threshold) try with "no data locality" at least
>> once before giving up. It will be a good idea to file a JIRA with this
>> requirement.
-Go
thinking about this some more, we could use our tracking of node
reliability to tune our placement decisions.
1. We add a "recent failures" field to the node entries, alongside the
"total failures"
2. Our scheduled failure count resetter will set that field to zero,
alongside the comp
37 matches
Mail list logo