It cannot be guaranteed that the previous port will still be available when
the application is thawed - in reality the application can 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 app
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
The Apache Jenkins build system has built Slider-develop (build #96)
Status: Still Failing
Check console output at https://builds.apache.org/job/Slider-develop/96/ to
view the results.
Thats been my experience too when I encounter this error. Also, I do not
see any System.exit() in code but then again I have not looked at the
libraries.
On Fri, Jul 11, 2014 at 2:35 PM, Josh Elser wrote:
> Heh, I just ran into this too. I couldn't find the dump from the JVM
> though.
>
>
> On
In appConfig.json, you can replace "0" with
${HBASE_REGIONSERVER.ALLOCATED_PORT} in which case, an explicit port will
be allocated and it will be discoverable using
ws/v1/slider/publisher/slider/hbase-site.xml
On Fri, Jul 11, 2014 at 3:46 PM, Ted Yu wrote:
> Hi,
> Certain test script hardcodes
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
[
https://issues.apache.org/jira/browse/SLIDER-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14059450#comment-14059450
]
ASF subversion and git services commented on SLIDER-121:
Commit 16
[
https://issues.apache.org/jira/browse/SLIDER-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14059447#comment-14059447
]
ASF subversion and git services commented on SLIDER-121:
Commit 16
The Apache Jenkins build system has built Slider-develop (build #95)
Status: Failure
Check console output at https://builds.apache.org/job/Slider-develop/95/ to
view the results.
[
https://issues.apache.org/jira/browse/SLIDER-227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14059433#comment-14059433
]
ASF subversion and git services commented on SLIDER-227:
Commit 16
[
https://issues.apache.org/jira/browse/SLIDER-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14059410#comment-14059410
]
ASF subversion and git services commented on SLIDER-121:
Commit 16
Heh, I just ran into this too. I couldn't find the dump from the JVM though.
On 7/11/14, 2:49 AM, Sumit Mohanty wrote:
The jenkins build for Slider is intermittently hitting the following issue:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.16:test
(default-tes
[
https://issues.apache.org/jira/browse/SLIDER-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14059298#comment-14059298
]
ASF subversion and git services commented on SLIDER-223:
Commit 0b
+1
On Fri, Jul 11, 2014 at 12:54 PM, Jon Maron wrote:
> +1
>
> On Jul 11, 2014, at 2:42 AM, Sumit Mohanty
> wrote:
>
> > Hello folks,
> >
> > This is a call for a vote on Apache Slider 0.40.0 incubating release.
> > Thanks to everyone who have contributed to this release.
> >
> > Git source ta
Sumit:
You can find doc on upgrade here:
http://hbase.apache.org/book.html#hbase.rolling.restart
bq. Are there two versions of HBase
You can upgrade from 0.98.2 to 0.98.3
0.98.4 RC0 would come out this weekend.
Cheers
On Fri, Jul 11, 2014 at 12:51 PM, Sumit Mohanty
wrote:
> Nice.
>
> As such
[
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 Definition
> ---
+1
On Jul 11, 2014, at 2:42 AM, Sumit Mohanty wrote:
> Hello folks,
>
> This is a call for a vote on Apache Slider 0.40.0 incubating release.
> Thanks to everyone who have contributed to this release.
>
> Git source tag:
> https://git-wip-us.apache.org/repos/asf?p=incubator-slider.git;a=shortl
Nice.
As such rolling upgrade needs some discussion. It will be good to have
update take a new "tarball" and then just upgrade the app instance -
running or not. But that might be a little far off. Are there two versions
of HBase that I can use today and upgrade from one to the other? Can you
shar
[
https://issues.apache.org/jira/browse/SLIDER-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14059258#comment-14059258
]
Sumit Mohanty commented on SLIDER-224:
--
+1. We may go with dedicated config files in
[
https://issues.apache.org/jira/browse/SLIDER-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14059181#comment-14059181
]
Steve Loughran commented on SLIDER-224:
---
I can see the appeal, but don't want to rus
[
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 u
[
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)
> Pr
[
https://issues.apache.org/jira/browse/SLIDER-227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14059172#comment-14059172
]
ASF subversion and git services commented on SLIDER-227:
Commit 16
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 capability to
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 appConfig
> --
[
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 appConfig
> ---
[
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 appConfig
> --
[
https://issues.apache.org/jira/browse/SLIDER-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser updated SLIDER-228:
--
Attachment: 0001-SLIDER-228-Lift-maven-compiler-plugin-definition-to-.patch
Patch that will fail the bu
In my opinion, action update should give user capability to perform rolling
upgrade :-)
Let me continue with this new action as outlined below.
On Fri, Jul 11, 2014 at 10:37 AM, Sumit Mohanty
wrote:
> One more argument is that we may limit what "update" can update - even if
> for no other reas
One more argument is that we may limit what "update" can update - even if
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 wha
On Jul 11, 2014, at 1:31 PM, Ted Yu wrote:
> The action update, at its full capacity, is what the current build action
> does:
> user may want to change hdfs, hbase config values and use new image
> (compatible with the previous image).
>
> One solution is to give action update the same capacit
The action update, at its full capacity, is what the current build action
does:
user may want to change hdfs, hbase config values and use new image
(compatible with the previous image).
One solution is to give action update the same capacity as action build -
without the constraint of aforemention
Why would I want to leverage “build” to update the cluster rather than the
discussed “update” action? In both instances I don’t imagine the parameter
change should take place prior to a restart. Correct?
— Jon
On Jul 11, 2014, at 1:19 PM, Ted Yu wrote:
> Hi,
> When I issue action build on a
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-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14059020#comment-14059020
]
Josh Elser commented on SLIDER-228:
---
It seems like it might not be quite as straightforw
[
https://issues.apache.org/jira/browse/SLIDER-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14058981#comment-14058981
]
Josh Elser commented on SLIDER-228:
---
Actually, looks like this can just be done with the
Josh Elser created SLIDER-228:
-
Summary: Set up enforcer plugin to assert that JDK7 is used to
build project
Key: SLIDER-228
URL: https://issues.apache.org/jira/browse/SLIDER-228
Project: Slider
[
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 s
Jonathan Maron created SLIDER-227:
-
Summary: create ssl architecture and user documentation
Key: SLIDER-227
URL: https://issues.apache.org/jira/browse/SLIDER-227
Project: Slider
Issue Type: D
[
https://issues.apache.org/jira/browse/SLIDER-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Maron resolved SLIDER-131.
---
Resolution: Fixed
> enable AM one and two-way SSL and test/enable agent secure comm
> ---
Hi,
Info on related to this error
http://maven.apache.org/surefire/maven-surefire-plugin/faq.html#vm-termination
On Fri, Jul 11, 2014 at 12:19 PM, Sumit Mohanty
wrote:
> The jenkins build for Slider is intermittently hitting the following issue:
>
> [ERROR] Failed to execute goal
> org.apache
42 matches
Mail list logo
