ssign the last
> port.
>
>
> On Sat, Jul 12, 2014 at 4:31 AM, Ted Yu wrote:
>
> > I agree with Jon's assessment.
> >
> > On Jul 12, 2014, at 4:28 AM, Jon Maron wrote:
> >
> > > That modification may make sense, but it still seems that the
> &
[
https://issues.apache.org/jira/browse/SLIDER-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated SLIDER-229:
--
Description:
During thaw action, if component instance is revived on the host where it last
ran and the port
Ted Yu created SLIDER-229:
-
Summary: Assign the previous port when thawing component instance
if port is available
Key: SLIDER-229
URL: https://issues.apache.org/jira/browse/SLIDER-229
Project: Slider
sult isn't "no region server".
>
> -- Jon
>
> On Jul 12, 2014, at 6:42 AM, Ted Yu wrote:
>
>> Alternatively the agent detects whether previous port is available, reuses
>> the same port if it is. Otherwise fallback to current behavior.
>>
>>
be thawed in few
>> minutes or even few days. So I think reusing the old port might be a risk.
>>
>> Isn't this a case for the QE script to change? Inherently, for yarn apps,
>> they need to handle dynamic host/port.
>>
>>
>> On Fri, Jul 11, 2014 at 9
Hi,
When I was debugging existing QE hbase test script, I found that in the
following situation (create - freeze - thaw) it was determined that there
was no live server:
region server, hor10n03.gq1.ygridcore.net,42175,1405108984098, was
considered dead by the new master due to 'freeze' action
the n
Hi,
Certain test script hardcodes region server info port @ 60030
This wouldn't work for region server in Slider deployed cluster.
I examined the output from 'slider status'
and ws/v1/slider/publisher/slider/hbase-site.xml
port information is not in status output.
>From the latter, I see:
hbase
other? Can you
> share some doc, if any, that describes the manual steps to do the upgrade.
>
> -Sumit
>
>
> On Fri, Jul 11, 2014 at 11:30 AM, Ted Yu wrote:
>
> > Update on the action 'update':
> > I verified that changing the
[
https://issues.apache.org/jira/browse/SLIDER-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated SLIDER-223:
--
Fix Version/s: Slider 0.50
> Provide action to update Instance Definit
[
https://issues.apache.org/jira/browse/SLIDER-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated SLIDER-223:
--
Description:
Here is one use case:
user freezes cluster and modifies some config values in appConfig.json
the
[
https://issues.apache.org/jira/browse/SLIDER-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated SLIDER-223:
--
Summary: Provide action to update Instance Definition (was: Provide action
to update template appConfig
Update on the action 'update':
I verified that changing the below hbase config takes effect after thawing
an existing cluster:
hbase.regionserver.global.memstore.lowerLimit0.39
Cheers
On Fri, Jul 11, 2014 at 10:39 AM, Ted Yu wrote:
> In my opinion, action update should give user
Hi,
You may have noticed that after a cluster is frozen / thawed,
the FinalStatus column shows FAILED.
We should fix this - or at least document it.
Cheers
[
https://issues.apache.org/jira/browse/SLIDER-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated SLIDER-223:
--
Attachment: slider-223-4.txt
> Provide action to update template appCon
[
https://issues.apache.org/jira/browse/SLIDER-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated SLIDER-223:
--
Attachment: (was: slider-223-4.txt)
> Provide action to update template appCon
[
https://issues.apache.org/jira/browse/SLIDER-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated SLIDER-223:
--
Attachment: slider-223-4.txt
> Provide action to update template appCon
gt; for no other reason other than just phasing in capabilities.
>
> -Sumit
>
>
> On Fri, Jul 11, 2014 at 10:33 AM, Jon Maron
> wrote:
>
> >
> > On Jul 11, 2014, at 1:31 PM, Ted Yu wrote:
> >
> > > The action update, at its full capacity, is what the
>
> — Jon
>
> On Jul 11, 2014, at 1:19 PM, Ted Yu wrote:
>
> > Hi,
> > When I issue action build on an existing cluster, I get:
> >
> > 2014-07-11 17:15:05,377 [main] ERROR main.ServiceLauncher - Application
> > Instance dir already exists: hdfs://
> &g
Hi,
When I issue action build on an existing cluster, I get:
2014-07-11 17:15:05,377 [main] ERROR main.ServiceLauncher - Application
Instance dir already exists: hdfs://
hor10n03.gq1.ygridcore.net:8020/user/yarn/.slider/cluster/cl1
2014-07-11 17:15:05,378 [main] INFO util.ExitUtil - Exiting with
[
https://issues.apache.org/jira/browse/SLIDER-226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated SLIDER-226:
--
Description:
build action paves the road for supporting rolling upgrade on Slider deployed
cluster.
User can
Ted Yu created SLIDER-226:
-
Summary: Provide mechanism for rolling upgrade
Key: SLIDER-226
URL: https://issues.apache.org/jira/browse/SLIDER-226
Project: Slider
Issue Type: Improvement
Hi,
Please take a look at patch v3 and provide your comments.
Thanks
On Thu, Jul 10, 2014 at 10:32 AM, Ted Yu wrote:
> Initial patch attached to SLIDER-223
>
> Please review.
>
>
>
[
https://issues.apache.org/jira/browse/SLIDER-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14058118#comment-14058118
]
Ted Yu commented on SLIDER-223:
---
With patch v3, I saw the following after thawing a fr
[
https://issues.apache.org/jira/browse/SLIDER-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated SLIDER-223:
--
Attachment: (was: slider-223-3.txt)
> Provide action to update template appCon
[
https://issues.apache.org/jira/browse/SLIDER-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated SLIDER-223:
--
Attachment: slider-223-3.txt
> Provide action to update template appCon
[
https://issues.apache.org/jira/browse/SLIDER-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated SLIDER-223:
--
Attachment: (was: slider-223-3.txt)
> Provide action to update template appCon
[
https://issues.apache.org/jira/browse/SLIDER-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated SLIDER-223:
--
Attachment: slider-223-3.txt
> Provide action to update template appCon
[
https://issues.apache.org/jira/browse/SLIDER-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated SLIDER-223:
--
Attachment: (was: slider-223-3.txt)
> Provide action to update template appCon
[
https://issues.apache.org/jira/browse/SLIDER-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated SLIDER-223:
--
Attachment: slider-223-3.txt
> Provide action to update template appCon
[
https://issues.apache.org/jira/browse/SLIDER-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated SLIDER-223:
--
Attachment: (was: slider-223-3.txt)
> Provide action to update template appCon
[
https://issues.apache.org/jira/browse/SLIDER-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated SLIDER-223:
--
Attachment: slider-223-3.txt
> Provide action to update template appCon
[
https://issues.apache.org/jira/browse/SLIDER-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated SLIDER-223:
--
Attachment: slider-223-3.txt
> Provide action to update template appCon
[
https://issues.apache.org/jira/browse/SLIDER-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14058075#comment-14058075
]
Ted Yu commented on SLIDER-223:
---
With patch v2, I got the following when thaw
[
https://issues.apache.org/jira/browse/SLIDER-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated SLIDER-223:
--
Attachment: slider-223-2.txt
> Provide action to update template appCon
[
https://issues.apache.org/jira/browse/SLIDER-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated SLIDER-223:
--
Attachment: (was: slider-223-2.txt)
> Provide action to update template appCon
[
https://issues.apache.org/jira/browse/SLIDER-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated SLIDER-223:
--
Attachment: (was: slider-223-2.txt)
> Provide action to update template appCon
[
https://issues.apache.org/jira/browse/SLIDER-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated SLIDER-223:
--
Attachment: slider-223-2.txt
> Provide action to update template appCon
[
https://issues.apache.org/jira/browse/SLIDER-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated SLIDER-223:
--
Attachment: slider-223-2.txt
Patch v2
> Provide action to update template appCon
[
https://issues.apache.org/jira/browse/SLIDER-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated SLIDER-223:
--
Attachment: (was: slider-223.txt)
> Provide action to update template appCon
[
https://issues.apache.org/jira/browse/SLIDER-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated SLIDER-223:
--
Attachment: slider-223.txt
> Provide action to update template appCon
[
https://issues.apache.org/jira/browse/SLIDER-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated SLIDER-223:
--
Attachment: (was: slider-223.txt)
> Provide action to update template appCon
[
https://issues.apache.org/jira/browse/SLIDER-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated SLIDER-223:
--
Attachment: slider-223.txt
> Provide action to update template appCon
Initial patch attached to SLIDER-223
Please review.
On Thu, Jul 10, 2014 at 8:25 AM, Sumit Mohanty
wrote:
> It would get merged with the cluster config in the cluster instance config
> in HDFS.
>
>
> On Thu, Jul 10, 2014 at 7:46 AM, Ted Yu wrote:
>
> > For sepa
[
https://issues.apache.org/jira/browse/SLIDER-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated SLIDER-223:
--
Attachment: slider-223.txt
Initial patch.
> Provide action to update template appCon
[
https://issues.apache.org/jira/browse/SLIDER-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu reassigned SLIDER-223:
-
Assignee: Ted Yu
> Provide action to update template appCon
[
https://issues.apache.org/jira/browse/SLIDER-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated SLIDER-223:
--
Summary: Provide action to update template appConfig (was: Allow
specification of appConfig when thawing
[
https://issues.apache.org/jira/browse/SLIDER-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated SLIDER-223:
--
Description:
Here is one use case:
user freezes cluster and modifies some config values in appConfig.json
the
Ted Yu created SLIDER-224:
-
Summary: Allow appConfig.json to contain external reference
Key: SLIDER-224
URL: https://issues.apache.org/jira/browse/SLIDER-224
Project: Slider
Issue Type: Task
anges will not take effect", but otherwise just
>> load/patch/save the config(s)
>>
>>
>>
>>
>> On 10 July 2014 00:50, Ted Yu wrote:
>>
>>> Hi,
>>> I want to get your opinion on whether 'thaw' command should support
Ted Yu created SLIDER-223:
-
Summary: Allow specification of appConfig when thawing cluster
Key: SLIDER-223
URL: https://issues.apache.org/jira/browse/SLIDER-223
Project: Slider
Issue Type: Task
Hi,
I want to get your opinion on whether 'thaw' command should support the
specification of template, as in:
--template appConfig.json
The use case would be: user changes some (hbase) config values and wants
the new values to take effect when the cluster is thaw'ed.
Please comment.
Hi,
Below is snippet of output from 'slider status cl3' .
Please note the host in bold.
However the actual master is on hor10n08 and backup master is on hor10n03.
What do I miss ?
Cheers
"HBASE_MASTER" : {
"container_1404945458343_0006_01_02" : {
"name" : "container_
Looks like a default value can be provided for SLIDER_CONF_DIR_PROP so that
'mvn test' can succeed.
On Wed, Jul 9, 2014 at 1:21 PM, Sumit Mohanty
wrote:
> Should we modify the code such that "mvn clean package" itself would run
> cleanly? (depends if its expected that "mvn clean install" or "mv
[
https://issues.apache.org/jira/browse/SLIDER-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14056590#comment-14056590
]
Ted Yu commented on SLIDER-220:
---
I logged SLIDER-222 for enhancing 'registry
[
https://issues.apache.org/jira/browse/SLIDER-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu resolved SLIDER-220.
---
Resolution: Fixed
> Provide script for retrieving hbase-site.xml given cluster n
Ted Yu created SLIDER-222:
-
Summary: Enhance registry command with --out option
Key: SLIDER-222
URL: https://issues.apache.org/jira/browse/SLIDER-222
Project: Slider
Issue Type: Task
[
https://issues.apache.org/jira/browse/SLIDER-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14056514#comment-14056514
]
Ted Yu commented on SLIDER-220:
---
This command works:
bin/slider registry --getconf h
[
https://issues.apache.org/jira/browse/SLIDER-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14056498#comment-14056498
]
Ted Yu commented on SLIDER-220:
---
{code}
2014-07-09 16:53:11,275 [main] D
[
https://issues.apache.org/jira/browse/SLIDER-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14056021#comment-14056021
]
Ted Yu edited comment on SLIDER-220 at 7/9/14 4:59 PM:
---
we ha
[
https://issues.apache.org/jira/browse/SLIDER-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14056445#comment-14056445
]
Ted Yu commented on SLIDER-220:
---
I tried the following two commands:
{code}
119
[
https://issues.apache.org/jira/browse/SLIDER-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated SLIDER-220:
--
Attachment: get-hbase-site.sh
> Provide script for retrieving hbase-site.xml given cluster n
Ted Yu created SLIDER-220:
-
Summary: Provide script for retrieving hbase-site.xml given
cluster name
Key: SLIDER-220
URL: https://issues.apache.org/jira/browse/SLIDER-220
Project: Slider
Issue Type
Hi,
Once I produce app package for hbase, the next build would complain about
the following.
Unapproved licenses:
app-packages/hbase/target/archive-tmp/appConfig.json.1746534752.filtered
app-packages/hbase/target/archive-tmp/appConfig.json.727813455.filtered
app-packages/hbase/target/maven-s
[
https://issues.apache.org/jira/browse/SLIDER-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu resolved SLIDER-217.
---
Resolution: Fixed
Assignee: Ted Yu
Verified that
target/apache-slider-hbase-0.98.3-hadoop2-app
[
https://issues.apache.org/jira/browse/SLIDER-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14054502#comment-14054502
]
Ted Yu commented on SLIDER-217:
---
Note the condition:
bq. After HBase tarball is publi
Ted Yu created SLIDER-215:
-
Summary: Add functional tests for HBase app package
Key: SLIDER-215
URL: https://issues.apache.org/jira/browse/SLIDER-215
Project: Slider
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/SLIDER-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu resolved SLIDER-212.
---
Resolution: Fixed
> Add hbase dependencies for slider-providers/hbase/hbase-funte
Ted Yu created SLIDER-212:
-
Summary: Add hbase dependencies for
slider-providers/hbase/hbase-funtests
Key: SLIDER-212
URL: https://issues.apache.org/jira/browse/SLIDER-212
Project: Slider
Issue
I saw the following errors using 'mvn clean package -DskipTests' under root
of workspace:
[ERROR]
/homes/hortonzy/slider/slider-providers/hbase/hbase-funtests/src/test/groovy/org/apache/slider/providers/hbase/funtest/HBaseCommandTestBase.groovy:[1,1]
3. ERROR in
/homes/hortonzy/slider/slider-provi
:2.8:copy (copy) @ slider-funtest ---
> [INFO] Configured Artifact:
> org.apache.slider:apache-slider-command-logger:?:zip
> [INFO]
> org.apache.slider:apache-slider-command-logger:0.31.0-incubating-SNAPSHOT:zip
> already exists in
> /Users/jmaron/dev/workspaces/slider-asf/incubator-slider/slider-fu
I have added a note to app-packages/hbase/README.txt
Cheers
On Mon, Jul 7, 2014 at 7:12 AM, Sumit Mohanty
wrote:
> You need to copy the hbase tarball to
> ~/.m2/repository/org/apache/hbase/hbase/0.98.3-hadoop2/.
> I do not know why it needs to be done as "mvn install:install-file ..."
> should
[
https://issues.apache.org/jira/browse/SLIDER-207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14051041#comment-14051041
]
Ted Yu commented on SLIDER-207:
---
In the test, I see this line:
{
Ted Yu created SLIDER-207:
-
Summary: TestClusterConnectivity fails on Jenkins
Key: SLIDER-207
URL: https://issues.apache.org/jira/browse/SLIDER-207
Project: Slider
Issue Type: Test
[
https://issues.apache.org/jira/browse/SLIDER-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated SLIDER-207:
--
Description:
>From https://builds.apache.org/job/Slider-develop/67/console :
{code}
Failed te
[
https://issues.apache.org/jira/browse/SLIDER-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14049075#comment-14049075
]
Ted Yu commented on SLIDER-173:
---
Created SLIDER-195 for "always demand prev
Ted Yu created SLIDER-195:
-
Summary: Add PlacementPolicy option "always demand previous host"
Key: SLIDER-195
URL: https://issues.apache.org/jira/browse/SLIDER-195
Project: Slider
Issue
Billie:
Can you post the stack trace for the exception ?
Thanks
On Mon, Jun 30, 2014 at 5:04 PM, Billie Rinaldi
wrote:
> Has anything happened with ALLOCATED_PORT recently? In my funtest, I'm
> getting an exception from Accumulo saying that the value for the monitor
> port property isn't in t
[
https://issues.apache.org/jira/browse/SLIDER-173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu resolved SLIDER-173.
---
Resolution: Fixed
> Container requests for the same role should utilize different no
Hi,
For user to retrieve effective hbase-site configuration, the following
needs to be done:
issue 'slider status' command
extract value for "info.am.web.url" from the output
append '/ws/v1/slider/publisher/slider/hbase-site' to the URL
The output from last step is JSON.
I want to get some sugge
[
https://issues.apache.org/jira/browse/SLIDER-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14047831#comment-14047831
]
Ted Yu edited comment on SLIDER-173 at 6/30/14 4:54 PM:
I did
[
https://issues.apache.org/jira/browse/SLIDER-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14047831#comment-14047831
]
Ted Yu commented on SLIDER-173:
---
Planning to resolve this JIRA.
> Container reque
[
https://issues.apache.org/jira/browse/SLIDER-173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu reassigned SLIDER-173:
-
Assignee: Ted Yu
> Container requests for the same role should utilize different no
; We need to understand where the log settings are coming from and make sure
> that the slider conf ones are the set being used.
>
>
> On 28 June 2014 15:57, Ted Yu wrote:
>
> > This seems to be a known issue - as confirmed by Sumit.
> >
> > I plan to add a comman
This seems to be a known issue - as confirmed by Sumit.
I plan to add a commandline flag which tells Slider to log at detail level
implemented through log.info() calls.
Please comment.
On Fri, Jun 27, 2014 at 1:46 PM, Ted Yu wrote:
> Hi,
> In conf/log4j.properties, I spe
Hi,
In conf/log4j.properties, I specified:
log4j.logger.org.apache.slider=DEBUG
log4j.logger.org.apache.slider.server.appmaster.state.RoleHistory=DEBUG,subprocess
But in AppMaster log, I don't see DEBUG logs from RoleHistory.
What did I miss ?
Cheers
[
https://issues.apache.org/jira/browse/SLIDER-174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14046101#comment-14046101
]
Ted Yu commented on SLIDER-174:
---
In HBase 1.0+, the master process is merged with re
[
https://issues.apache.org/jira/browse/SLIDER-173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated SLIDER-173:
--
Attachment: (was: slider-173-v3.txt)
> Container requests for the same role should utilize different no
[
https://issues.apache.org/jira/browse/SLIDER-173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated SLIDER-173:
--
Attachment: slider-173-v3.txt
> Container requests for the same role should utilize different no
[
https://issues.apache.org/jira/browse/SLIDER-173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated SLIDER-173:
--
Attachment: slider-173-v3.txt
> Container requests for the same role should utilize different no
[
https://issues.apache.org/jira/browse/SLIDER-173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated SLIDER-173:
--
Attachment: (was: slider-173-v2.txt)
> Container requests for the same role should utilize different no
[
https://issues.apache.org/jira/browse/SLIDER-173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated SLIDER-173:
--
Attachment: slider-173-v2.txt
> Container requests for the same role should utilize different no
[
https://issues.apache.org/jira/browse/SLIDER-173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated SLIDER-173:
--
Attachment: (was: slider-173-v2.txt)
> Container requests for the same role should utilize different no
[
https://issues.apache.org/jira/browse/SLIDER-173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated SLIDER-173:
--
Attachment: slider-173-v2.txt
> Container requests for the same role should utilize different no
[
https://issues.apache.org/jira/browse/SLIDER-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14045289#comment-14045289
]
Ted Yu commented on SLIDER-173:
---
Patch v2 implements separate Priority by taking
[
https://issues.apache.org/jira/browse/SLIDER-173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated SLIDER-173:
--
Attachment: slider-173-v2.txt
> Container requests for the same role should utilize different no
[
https://issues.apache.org/jira/browse/SLIDER-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14045281#comment-14045281
]
Ted Yu commented on SLIDER-173:
---
The side effect is due to AMRMClient
[
https://issues.apache.org/jira/browse/SLIDER-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14044993#comment-14044993
]
Ted Yu commented on SLIDER-173:
---
Saw this in today's test:
{code}
14/06/26 18:1
[
https://issues.apache.org/jira/browse/SLIDER-174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14044917#comment-14044917
]
Ted Yu commented on SLIDER-174:
---
bq. Seems like there's a need for another flag
[
https://issues.apache.org/jira/browse/SLIDER-174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14044888#comment-14044888
]
Ted Yu commented on SLIDER-174:
---
bq. a request is made for a specific host then loca
[
https://issues.apache.org/jira/browse/SLIDER-174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu resolved SLIDER-174.
---
Resolution: Fixed
> HBase Master needs data local
301 - 400 of 464 matches
Mail list logo
