Phase 2 of read replica hasn't been fully integrated to Apache HBase yet.
Once that is done, you can produce hbase app package and utilize this
feature.
FYI
On Tue, Jan 6, 2015 at 7:52 PM, liujs3 wrote:
> Yes ,I mean that read replica
>
>
>
>
> -邮件原件-
> 发件人: Ted Yu [mailto:yuzhih...@gma
Yes ,I mean that read replica
-邮件原件-
发件人: Ted Yu [mailto:yuzhih...@gmail.com]
发送时间: 2015年1月7日 10:53
收件人: dev@slider.incubator.apache.org
主题: Re: the component ha
w.r.t. region ha, did you mean read replica ?
bq. how config the backhmaster
Did you mean secondary master ? You can spec
w.r.t. region ha, did you mean read replica ?
bq. how config the backhmaster
Did you mean secondary master ? You can specify 2 instances of HBASE_MASTER
in resources.json
Cheers
On Tue, Jan 6, 2015 at 6:39 PM, liujs3 wrote:
> hi， i see the least news about hbase ，it will support region ha，whe
Nitin,
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.
-Gour
On Tue, Jan 6, 2015 at 5:12 PM, Nitin Aggarwal wro
hi， i see the least news about hbase ，it will support region ha，when flex 2
regionserver on a host ，it there something wrong？
2. and now container can failed-restart，is unuseful for the component ha？ eg
hmaster？
now how config the backhmaster for hbase？
Anti-affinity has not been implemented yet.
Cheers
On Tue, Jan 6, 2015 at 5:26 PM, 杨浩 wrote:
> I have read the PlacementPolicy.java, but it seems there is no call to
> ANTI_AFFINITY_REQUIRED
>
> 2015-01-07 8:52 GMT+08:00 Ted Yu :
>
> > Here is the meaning of 2 (see PlacementPolicy):
> >
> >
I have read the PlacementPolicy.java, but it seems there is no call to
ANTI_AFFINITY_REQUIRED
2015-01-07 8:52 GMT+08:00 Ted Yu :
> Here is the meaning of 2 (see PlacementPolicy):
>
>* No data locality; do not bother trying to ask for any location
>
>*/
>
> public static final int NO_DAT
I am running HBase application, and I prefer data locality. I don't want to
give up locality by default. It's ok to lose locality in rare scenarios,
where something is wrong with one of the local nodes.
It's more of fail-safe that I am looking for, to give up locality, if it
cannot be satisfied.
T
Here is the meaning of 2 (see PlacementPolicy):
* No data locality; do not bother trying to ask for any location
*/
public static final int NO_DATA_LOCALITY = 2;
On Tue, Jan 6, 2015 at 4:15 PM, Gour Saha wrote:
> Try setting property *yarn.component.placement.policy* to 2 for the
> co
+1 for getting rid of the /agent one
On Tue, Jan 6, 2015 at 9:23 AM, Sumit Mohanty
wrote:
> Yes, the /agent one can be removed.
>
> On Tue, Jan 6, 2015 at 7:26 AM, Jon Maron wrote:
>
> >
> > On Jan 6, 2015, at 9:54 AM, Steve Loughran
> wrote:
> >
> > > https://issues.apache.org/jira/browse/SLI
Try setting property *yarn.component.placement.policy* to 2 for the
component, something like this -
"HBASE_MASTER": {
"yarn.role.priority": "1",
"yarn.component.instances": "1",
"yarn.memory": "1500",
"yarn.component.placement.policy": "2"
},
-Gour
On Tue, Jan 6,
Hi,
We keep on running into scenario, where one of the node in the cluster went
bad (either due to clock out of sync, no disk space etc.). As a result
container fails to start, and due to locality, container is assigned on the
same machine again and again, and it fails again and again. After few
f
The Apache Jenkins build system has built Slider-develop (build #511)
Status: Failure
Check console output at https://builds.apache.org/job/Slider-develop/511/ to
view the results.
[
https://issues.apache.org/jira/browse/SLIDER-741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran resolved SLIDER-741.
---
Resolution: Fixed
> expose raw/resolved views of app configurations
>
[
https://issues.apache.org/jira/browse/SLIDER-741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14266615#comment-14266615
]
ASF subversion and git services commented on SLIDER-741:
Commit 0d
[
https://issues.apache.org/jira/browse/SLIDER-741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran updated SLIDER-741:
--
Summary: expose raw/resolved views of app configurations (was: expose
resolved view of app conf
Yes, the /agent one can be removed.
On Tue, Jan 6, 2015 at 7:26 AM, Jon Maron wrote:
>
> On Jan 6, 2015, at 9:54 AM, Steve Loughran wrote:
>
> > https://issues.apache.org/jira/browse/SLIDER-641 covers the fact that we
> > have two slider-agent.tar.gz files in the tar, one in /lib, the other in
On Jan 6, 2015, at 9:54 AM, Steve Loughran wrote:
> https://issues.apache.org/jira/browse/SLIDER-641 covers the fact that we
> have two slider-agent.tar.gz files in the tar, one in /lib, the other in
> /agent.
>
> I want to cut one: which one should I keep? I'm assuming the agent one
+1
>
>
Steve Loughran created SLIDER-741:
-
Summary: expose resolved view of app configurations
Key: SLIDER-741
URL: https://issues.apache.org/jira/browse/SLIDER-741
Project: Slider
Issue Type: Sub-t
[
https://issues.apache.org/jira/browse/SLIDER-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran updated SLIDER-151:
--
Sprint: Slider December #1, Slider Jan #1 (was: Slider December #1)
> Implement full slider API
[
https://issues.apache.org/jira/browse/SLIDER-739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran updated SLIDER-739:
--
Remaining Estimate: 672h
Original Estimate: 672h
Estimating 4w of work; including tests and
[
https://issues.apache.org/jira/browse/SLIDER-739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14266194#comment-14266194
]
Steve Loughran commented on SLIDER-739:
---
Requirements
# In-cluster API for talking t
https://issues.apache.org/jira/browse/SLIDER-641 covers the fact that we
have two slider-agent.tar.gz files in the tar, one in /lib, the other in
/agent.
I want to cut one: which one should I keep? I'm assuming the agent one
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use
[
https://issues.apache.org/jira/browse/SLIDER-740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yang Hao updated SLIDER-740:
Attachment: (was: SLIDER-740.patch)
> support configurating HBASE_OPTS
> ---
Yang Hao created SLIDER-740:
---
Summary: support configurating HBASE_OPTS
Key: SLIDER-740
URL: https://issues.apache.org/jira/browse/SLIDER-740
Project: Slider
Issue Type: Improvement
Compo
[
https://issues.apache.org/jira/browse/SLIDER-740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yang Hao updated SLIDER-740:
Attachment: SLIDER-740.patch
> support configurating HBASE_OPTS
>
>
>
[
https://issues.apache.org/jira/browse/SLIDER-740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yang Hao updated SLIDER-740:
Attachment: SLIDER-740.patch
> support configurating HBASE_OPTS
>
>
>
Steve Loughran created SLIDER-739:
-
Summary: REST API to support application self-management
Key: SLIDER-739
URL: https://issues.apache.org/jira/browse/SLIDER-739
Project: Slider
Issue Type:
Steve Loughran created SLIDER-738:
-
Summary: (protototype) Registry REST API to serve up 302 redirects
to service endpoints
Key: SLIDER-738
URL: https://issues.apache.org/jira/browse/SLIDER-738
Projec
29 matches
Mail list logo
