Re: [VOTE] Move Apache Ambari to Attic

+1 to retire Ambari to the attic... Bittersweet, but it is time. On Mon, Jan 10, 2022 at 1:36 PM Jayush Luniya wrote: > Hi all, > > Following the process outlined here, https://attic.apache.org/process.html > , > I'm calling a vote to move Apache Ambari to the Attic. Over the past 2 > years we

Re: Ambari 2.7.6 Maintenance Release

+1 to the proposal and release of Ambari 2.7.6 in order to support users who either have their own stacks or are using a stack not behind a paywall. On Mon, Sep 20, 2021 at 9:24 AM Szabolcs Beki wrote: > Hello Ambari Devs and PMCs, > > It has been quite a long time since the last Ambari

Re: Contributor Access to Apache Ambari

I've added the user vjasani to the Contributors role of the project in Jira. This should allow assignment of issues. On 12/3/18, 3:57 AM, "Doroszlai Attila" wrote: Hi Vivek, Someone needs to assign vjasani to the Ambari project in Apache Jira to be able to take issues.

Ambari trunk Snapshot Versioning

It looks like Ambari’s trunk pom.xml has not been updated with a proper version in at least 4 years. It currently still lists trunk as 2.0.0.0-SNAPSHOT: https://github.com/apache/ambari/blob/trunk/pom.xml#L24 This poses several problems as we try to make our artifacts more 3rd-party friendly

Re: Stack Advisor during Rolling upgrade

Stack upgrades do not invoke the service advisor. If you need to set configurations, you either need to do so in the config-upgrade.xml for the stack, or provide a custom class which extends AbstractUpgradeServerAction and specify that class as part of the upgrade.xml. On 10/12/18, 8:23 AM,

New Ambari Module

Hi Developers, A new maven module has been created via https://issues.apache.org/jira/browse/AMBARI-24685 to allow us to provide a plugin framework for stack/mpack authors who need to provide their own compiled classes to Ambari. For areas such as upgrade pre-checks and server-side

Re: [VOTE] Apache Ambari 2.7.1 RC0

+1 for RC0 - SHA verified - Performed build - Compared files against git for diffs (none besides build artifacts) On 8/21/18, 3:25 PM, "Olivér Szabó" wrote: Hi All, I have created an apache-ambari-2.7.1 release candidate. GIT source tag: (release-2.7.1-rc0) :

Re: Unable to ignore and proceed when a rolling upgrade task fails

Ambari does actually give you the options to Ignore and Proceed if the failed task is marked as skippable in the upgrade pack XML file. Can you provide the specifics of the upgrade in terms of stack version, service/component experiencing the problem, etc? On 6/7/18, 2:59 AM, "Abhey Rana"

Github Commits without IDs

Hi committers, I’ve noticed a few commits going into Apache lately that are not following the format of [AMBARI-] – The title of my Jira This makes it difficult to correlate a commit to the actual Jira which it was for. As an example of the current git log (red text has no Jira):

Re: [VOTE] Apache Ambari 2.6.2 RC0

+1 for 2.6.2 On 4/27/18, 1:01 AM, "Swapan Shridhar" wrote: Hi All, I have created an apache-ambari-2.6.2 release candidate. GIT source tag (release-2.6.2-rc0) : https://github.com/apache/ambari/commits/release-2.6.2-rc0 Staging site:

Re: Rogue Branches Showing Up Again

or "Squash and Merge" (in the case of multiple commits) is enough. If you do an action through Github like a Revert, please double check that you have not created a branch in origin. On 4/11/18, 10:37 AM, "Jonathan Hurley" <jhur...@hortonworks.com> wrote: Hi commit

Re: pull requests without description

Agreed - the reviews without +1's are most concerning. We can't be committing without proper reviews. I think the only exceptions are: - reverts - merges from a main branch to a feature branch > On Apr 11, 2018, at 11:28 AM, Robert Levas wrote: > > +1 > > On 4/11/18,

Rogue Branches Showing Up Again

Hi committers, It looks like we have some rogue branches showing up again (perhaps the result of our trial and error with the new pull request model). In any event, here are the branches I am nominating for removal. If you don't want one of these removed, please respond to this email:

Re: why stack_root does not exist

The only scripts which should use /usr/hdp as a hard coded value are those which belong specifically to the HDP stack. Otherwise it's a bug and needs to be corrected. > On Mar 22, 2018, at 9:34 PM, xiang@sky-data.cn wrote: > > But i find some python script use "/usr/hdp" as hard code, is

Re: [VOTE] add FreeBuilder to Ambari

I agree - you can move mine to a -1 ... I'm having plenty of problems with FreeBuilder in Eclipse. > On Mar 20, 2018, at 8:20 PM, Doroszlai, Attila <adorosz...@apache.org> wrote: > > Let's close this vote: > > +1: Balazs Bence Sari, Attila Doroszlai > 0: Nate Cole, Jona

Re: trim Jenkins build logs

necessary changes. >> >> Thanks, >> Yusaku >> >> On 3/6/18, 11:26 AM, "Doroszlai, Attila" <adorosz...@apache.org> wrote: >> >>Yusaku, could you please make the change, or ask someone with access >>to Jenkins to do it

Re: [VOTE] add FreeBuilder to Ambari

0 - I am indifferent as well, but I remain cautious about integrating 3rd party build assistants into our ecosystem. Unlike using a library, this is something that is required for our IDEs to be compatible with. A change to an IDE or even JDK version could potentially cause the JAR to no longer

Re: New Branches Appearing

Anyone want to claim these branches? If not, I'd like to remove them. > On Feb 27, 2018, at 9:48 AM, Jonathan Hurley <jhur...@hortonworks.com> wrote: > > Hi committers and contributors, > > I noticed today that Ambari has had a few new branches created which don't > s

Re: IDE setup required on branch-feature-AMBARI-14714

I think this is something that should get voted on before it goes back into trunk. In general, it's risky to have to depend on 3rd party plugins to have a working, compiling project. If the contributors of FreeBuilder ever decide to abandon the project or if Eclipse or IntelliJ become

New Branches Appearing

Hi committers and contributors, I noticed today that Ambari has had a few new branches created which don't seem to be proper feature branches. They are: my_trunk vbrodetskyi-branch-2.6 We recently went through and cleaned out a whole bunch of stale branches and we want to keep our branch list

Re: [VOTE] Remove Groovy Shell and Groovy Client Modules from Ambari

+1 for removal. > On Feb 26, 2018, at 12:38 PM, Sandor Molnar wrote: > > +1, Remove ambari-shell and ambari-client modules > > On 2/26/18, 6:00 PM, "Doroszlai, Attila" wrote: > >+1 for removing ambari-shell and ambari-client modules. > >

Re: trim Jenkins build logs

+1 as well. Could we also set a property so that it doesn't try to weave every since class? Can we scope it only to the ORM classes? > On Feb 15, 2018, at 11:16 AM, Yusaku Sako wrote: > > +1 on changing log level. Good idea. > > Yusaku > > On 2/15/18, 8:02 AM,

Re: Removal of old/defunct branches

Last call before the following branches are removed: ambari-websocket ambari-yarnapps audit_logging branch-embedded-views branch-rbac-sso branch-yarnapps-dev side-navigation-feature-branch These have not seen a commit in roughly 2 years or more ... On Jan 25, 2018, at 9:15 AM, Jonathan Hurley

Re: [DISCUSS] Splitting the repos - ambari-metrics and ambari-logsearch

+1 - I definitely think that splitting their off is a great idea. > On Jan 26, 2018, at 10:20 AM, Nate Cole wrote: > > +1 > > On 1/26/18, 12:19 AM, "Siddharth Wagle" wrote: > >Hi devs, > > >We had a brief discussion about the release

Re: Removal of old/defunct branches

ambari-yarnapps audit_logging branch-embedded-views branch-rbac-sso branch-yarnapps-dev side-navigation-feature-branch Please let me know if there are any objections to removing the above branches as well. > On Jan 24, 2018, at 1:59 PM, Jonathan Hurley <jhur...@hortonworks.com> wrote

Removal of old/defunct branches

Hi committers and contributors, Ambari seems to have a bunch of branches that are dead and don't seem to serve any useful purposes. These include: origin/AMBARI-12885 origin/trunk remote/branch-2.4 remote/branch-2.5 trunkj trunkpwd They all seem to be either wrong (including the name of the

Re: Feature Branch Merging and PR

> apache/ambari? > > > On 1/18/18, 12:27 PM, "Jonathan Hurley" <jhur...@hortonworks.com> wrote: > >It's a bit odd though to create a PR every time you have to update a > branch. Depending on what you're working on, it may be fast-forwards each > time. To cre

Re: Feature Branch Merging and PR

It's a bit odd though to create a PR every time you have to update a branch. Depending on what you're working on, it may be fast-forwards each time. To create a PR each time seems like overkill. > On Jan 18, 2018, at 10:16 AM, Robert Levas wrote: > > I have been doing

Re: Add reviewers to PR as a non-committer?

b.com/apache/spark/pull/20297 On Wed, Jan 17, 2018 at 12:00 PM, Jonathan Hurley <jhur...@hortonworks.com> wrote: We have a very active project with potentially dozens of new PRs coming in every day - I don't think relying on the community to look is a very sustainable model. Is there no wa

Re: Add reviewers to PR as a non-committer?

We have a very active project with potentially dozens of new PRs coming in every day - I don't think relying on the community to look is a very sustainable model. Is there no way to add reviewers without tagging them? There seems to be a way to filter by reviews needing attention - seems silly

Re: [VOTE] Move ASF Github Bot comments to Worklog in JIRA

+1 - we definitely don't want these in the comments section! > On Jan 9, 2018, at 12:49 PM, Nate Cole wrote: > > +1 > > On 1/9/18, 11:56 AM, "Sandor Molnar" wrote: > >+1 > >I believe this is a really good idea. > >Sandor > >

Re: [DISCUSS] Future code review and commit process

nyl0_160c3724ae47072e] I agree with you on creating a wiki page to cover all the scenarios. ​ Thanks, Vivek Ratnavel On Thu, Jan 4, 2018 at 1:05 PM, Jonathan Hurley <jhur...@hortonworks.com<mailto:jhur...@hortonworks.com><mailto:jhur...@hortonworks.com>> wrote: Thanks for th

Re: [DISCUSS] Future code review and commit process

Thanks for the clarifications. This sounds like the "Forking Workflow" as opposed to the "Feature Branch Workflow". I'm fine with that since it lets non-commiters help. We should try to capture all of these scenarios in a wiki page which we can then all agree upon. Things which we need to

Re: [DISCUSS] Future code review and commit process

Yes, I mis-read the original email from Vivek. You have to work in your own fork of Ambari. Every pull request is done between the public branch and a branch in your local forked repo, right? > On Jan 4, 2018, at 11:32 AM, Attila Doroszlai > wrote: > >> * Since

Re: [DISCUSS] Future code review and commit process

This model is quite different from the model which many of us have been using years. As such, I think we need to define a bit more structure so that we keep the project tidy and under control. A few points: * Since this new flow model requires a branch for a commit, we should enforce a

Re: [VOTE] Migrate to gitbox

+1 > On Dec 7, 2017, at 6:48 PM, Vivek Ratnavel wrote: > > Hi all, > > I am starting this vote to migrate Apache Ambari project from git-wip > repository to gitbox, which allows a deeper integration with github > features. Moving to gitbox will allow committers to

Re: In-memory Persistence Type

I believe that this database type is only ever used for unit tests. > On May 18, 2017, at 1:57 PM, Anita Jebaraj wrote: > > Hello everyone, > > I came across the below piece of code in AmbariServer.java, > Can someone point me to some documentation on In-memory

Re: [VOTE] Apache Ambari 2.5.0 RC2

;> +1 for RC2. >> Verified checksums, signature, verified that .git artifacts no longer >> exist. >> >> Yusaku >> >> >> >> >> On 3/28/17, 9:47 AM, "Jonathan Hurley" <jhur...@hortonworks.com> wrote: >> >>> +1

Re: [VOTE] Apache Ambari 2.5.0 RC2

+1 for RC2 - verified source compared to Git as well as checksums. On Mar 28, 2017, at 11:18 AM, Roman Shaposhnik > wrote: On Mon, Mar 27, 2017 at 5:57 PM, Aravindan Vijayan > wrote:

Re: Why are AMS and LogSearch not part of RU/EU

They're not going to be part of those stacks for much longer. As Ambari moves toward management packs in 3.0, they'll be their own stack essentially. To your question - services can provide their own upgrade packs. Since these services are not part of the actual HDP stack, they should not be a

Re: Old Cluster name appering in logs even after Ambari-Server Reset Query!

That is correct - the agents queue some information. Once your new server started heartbeating, they delivered their payload which contained information from the last cluster. Once delivered, things should clear up. > On Feb 2, 2017, at 11:44 PM, Sumit Mohanty wrote:

Re: How to tell when Ambari server DB was upgraded

There was an initiative to capture this information: AMBARI-16030 ... but this seems to have stalled. If you still have the logs from Ambari Server, you can see when upgrades run by looking for text similar to: Upgrading schema to target version = 2.4.2.0 On Feb 2, 2017, at 10:56 AM, Di Li

Re: Requesting help regaring remote Debugging ambari-server

hostname, port and clicked debug. > > Also JDK version in host 1.8_111 and vm 1.8_77 is little different . > > > > > On 01-Feb-2017 10:24 PM, "Jonathan Hurley" <jhur...@hortonworks.com> wrote: > >> When I execute the same command that you do to s

Re: Requesting help regaring remote Debugging ambari-server

place what has step by step > instructions documented for me to follow. > > > > On 01-Feb-2017 9:55 PM, "Jonathan Hurley" <jhur...@hortonworks.com> wrote: > >> Everything looks correct here then - it actually says that you've already >> established a socket connec

Re: Requesting help regaring remote Debugging ambari-server

Yup! Here's the output. $ netstat -anp | grep 5005 (Not all processes could be identified, non-owned process infowill not be shown, you would have to be root to see it all.) tcp0 0 192.168.70.101:*5005* 192.168.70.1:50088 ESTABLISHED - Regards, Sandeep. On Wed, Feb 1, 2017 at 9:43 PM

Re: Requesting help regaring remote Debugging ambari-server

Refer attached screenshot in original mail. Still > facing the issue. > > On 01-Feb-2017 9:27 PM, "Jonathan Hurley" <jhur...@hortonworks.com> wrote: > >> Which port are you trying to connect to? When starting Ambari Server with >> debug on, a different por

Re: Requesting help regaring remote Debugging ambari-server

Which port are you trying to connect to? When starting Ambari Server with debug on, a different port is used for JDWP. You need to connect on port 5005. Here's an excerpt from the startup command: -Xdebug -Xrunjdwp:transport=dt_socket,address=5005 On Feb 1, 2017, at 10:05 AM, Sandy

Re: Upgrade mpack stack addon service

Ambari 3.0 is being targeted for allowing patch and service upgrades (independent of the rest of the cluster). This would also include the ability to upgrade a service which was deployed in an mpack. Currently, there is no way to include an mpack service in an Ambari-orchestrated upgrade.

Maven test Phase Checks for Style Issues...

Hi Developers, AMBARI-19149 along with a few other Jiras have recently been checked-in allowing our builds to fail when we have checkstyle violations. Right now, we're using this framework to check for things like: - private @Transactional methods - Switch statement fall-through - Import

Re: Git Feature Branches

ly, please flag it as an issue before the patch can be committed. Thanks! - Jonathan > On Sep 26, 2016, at 9:11 AM, Jonathan Hurley <jhur...@hortonworks.com> wrote: > > Hi Apache developers, > > I put together a simple wiki page outlining the strategy for using feature > b

Re: Git Feature Branches

to that branch should be related > to child JIRAs of that Epic. Would this be a good approach to take, or would > the additional Epic create too much unnecessary overhead? > > Rob > > > On 9/26/16, 9:11 AM, "Jonathan Hurley" <jhur...@hortonworks.com> wro

Git Feature Branches

Hi Apache developers, I put together a simple wiki page outlining the strategy for using feature branches which I think will help us keep our trunk branch stable as we move forward with new development: https://cwiki.apache.org/confluence/display/AMBARI/Git+Feature+Branches Please have a look

Re: [VOTE] Apache Ambari 2.4.0 RC0

+1 for RC0 Verified hashes, source files, and pom.xml to include 2.4.0.0.0 > On Aug 25, 2016, at 1:38 AM, Mithun Mathew wrote: > > Looks like the only choice is fixing it in the next release rather than > delaying the current release to fix it. > Something to be noted: We

Approval for AMBARI-18184

I would like to include AMBARI-18184 in the 2.4.0 release.

Re: Ambari-server schema upgrade failed -2.2.1.1

Ensure that this MySQL JAR file is specified in your /etc/ambari-server/conf/ambari.properties: db.mysql.jdbc.name=/var/lib/ambari-server/resources/mysql-connector-java-5.1.36-bin.jar On May 25, 2016, at 2:23 PM, Anandha L Ranganathan >

Re: Ambari upgrade 2.4 - not yet finalized

You hitting an instance of https://issues.apache.org/jira/browse/AMBARI-15482 I don't know of a way around this aside from: - Finalizing the upgrade - Starting NameNode manually from the command prompt It's probably best to just finalize the upgrade and start NameNode from the web client after

Re: [VOTE] Apache Ambari 2.2.2 RC1

+1 for RC1 > On Apr 25, 2016, at 8:37 PM, Srimanth Gunturi > wrote: > > Hello, > > I have created an ambari-2.2.2 release candidate RC1. > > GIT source tag (release-2.2.2-rc1) >

Re: Missed commit to 2.2.2 branch

ago: AMBARI-15954: PXF Check fails on Kerberized cluster without a YARN component (Lav Jain via mithmatt) * 34ac6f4 Jonathan Hurley 26 hours ago: AMBARI-15980 - RU/EU Precheck fails on Ranger Admin with SSL Because Of Missing Truststore (jonathanhurley) * 8e821e0 Sumit Mohanty 26 hours ago: AMB

Failing Unit Tests

Hi All, We have some failing tests consistently on b.a.o for both trunk and branch-2.2 (and possible branch-2.2.2). Here is the list of bugs created to track these. They've been failing for a while, so I think it's best to fix the tests instead of trying to backtrack and revert. If the bug is

AMBARI-15864 for Ambari 2.2.2

All, I have AMBARI-15864 as a candidate for Ambari 2.2.2; I will be committing this to branch-2.2 (as well as branch-2.2.2 when it is created). If there are objections, please let me know. Thanks, - Jonathan

Re: No killing topologies manual step for Storm in HDP 2.3 rolling upgrade

That is correct. Storm data wasn't portable between HDP 2.2 and HDP 2.3, so we needed to remove all storm data from ZK. HDP 2.3+ we no longer have to do this. > On Mar 10, 2016, at 2:48 PM, Di Li wrote: > > Hello folks, > > I noticed the manual step "Before

Review Request 44472: Kerberos Tickets Expire Too Frequently For Alerts

:924 Total errors:0 Total failures:0 OK Thanks, Jonathan Hurley

[jira] [Created] (AMBARI-15324) Kerberos Tickets Expire Too Frequently For Alerts

Jonathan Hurley created AMBARI-15324: Summary: Kerberos Tickets Expire Too Frequently For Alerts Key: AMBARI-15324 URL: https://issues.apache.org/jira/browse/AMBARI-15324 Project: Ambari

Re: Review Request 44459: Kerberos: Provide SHA256 or SHA512 options for template principal digest

/serveraction/kerberos/ADKerberosOperationHandler.java (lines 272 - 273) <https://reviews.apache.org/r/44459/#comment184363> Where do these values get used/exposed? Generating them is fine, but is there another Jira tracking how they are consumed? - Jonathan Hurley On March 7, 2016,

[jira] [Updated] (AMBARI-15303) New Alerts Do Not Honor Existing Maintenance Mode Setting

[ https://issues.apache.org/jira/browse/AMBARI-15303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley updated AMBARI-15303: - Attachment: AMBARI-15303.patch > New Alerts Do Not Honor Existing Maintenance M

Re: Review Request 44397: New Alerts Do Not Honor Existing Maintenance Mode Setting

-- [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 30:06 min [INFO] Finished at: 2016-03-04T13:32:30-05:00 [INFO] Final Memory: 50M/607M [INFO] Verified fix in an existing cluster by disabling alerts, then re-enabling them on a MM component with an active alert. Thanks, Jonathan Hurley

Re: Review Request 44397: New Alerts Do Not Honor Existing Maintenance Mode Setting

ceStateHelperTest.java d9c5039 ambari-server/src/test/java/org/apache/ambari/server/state/alerts/AlertReceivedListenerTest.java 6e58876 Diff: https://reviews.apache.org/r/44397/diff/ Testing --- PENDING: Writing UTs and running tests now... Verified fix in an existing cluster by disabling alerts, then re-enabling them on a MM component with an active alert. Thanks, Jonathan Hurley

Re: Review Request 44397: New Alerts Do Not Honor Existing Maintenance Mode Setting

--------- On March 4, 2016, 12:46 p.m., Jonathan Hurley wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/44397/ >

Review Request 44397: New Alerts Do Not Honor Existing Maintenance Mode Setting

cd49e76 ambari-server/src/main/java/org/apache/ambari/server/events/listeners/alerts/AlertReceivedListener.java 9bbfe37 Diff: https://reviews.apache.org/r/44397/diff/ Testing --- PENDING: Writing UTs and running tests now... Verified fix in an existing cluster by disabling alerts, then re-enabling them on a MM component with an active alert. Thanks, Jonathan Hurley

[jira] [Created] (AMBARI-15303) New Alerts Do Not Honor Existing Maintenance Mode Setting

Jonathan Hurley created AMBARI-15303: Summary: New Alerts Do Not Honor Existing Maintenance Mode Setting Key: AMBARI-15303 URL: https://issues.apache.org/jira/browse/AMBARI-15303 Project: Ambari

Re: Review Request 44392: Alert "Metadata Server Web UI" using hardcoded value for port

/ATLAS/0.1.0.2.3/alerts.json (lines 40 - 41) <https://reviews.apache.org/r/44392/#comment184005> Any reason the host name was removed? It's probably fine since the alert will default to the host it's running on. Just curious. - Jonathan Hurley On March 4, 2016, 10:44 a.m., Vitalyi Brod

Re: Review Request 44188: Provide details on the JCE policy installed in the JVM used by Ambari

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/44188/#review122068 --- Ship it! Ship It! - Jonathan Hurley On March 4, 2016, 5:17

Re: How do outsiders actually get stuff committed?

There are a lot of patches for Ambari; more than most of us can take a look at during a given day. Adding the "Ambari" group is probably not enough because of this; you'll want to add specific committers to your review list. I'd take a look at the reviews which have been submitted recently and

Re: Review Request 42031: [AMBARI-12915] Make agent hostname configurable

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/42031/#review121933 --- Ship it! Ship It! - Jonathan Hurley On Jan. 7, 2016, 3:17

Re: Review Request 44356: Add a WEB alert for Grafana

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/44356/#review121932 --- Ship it! Ship It! - Jonathan Hurley On March 3, 2016, 3:32

Re: Separate Issues Mailing list

+1 for that idea - it will make our client mail rules a bit less complex. > On Mar 3, 2016, at 7:09 AM, Lars Francke wrote: > > Hi everyone, > > the dev@ mailing list is pretty busy with JIRA traffic. How do you feel > about moving that traffic to a separate mailing

Re: Review Request 44057: AMBARI-15197 : Make use of log dir properties while installing Ranger

of the stack? - Jonathan Hurley On Feb. 26, 2016, 1:19 a.m., Gautam Borad wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://re

Re: Review Request 44060: AMBARI-15199 : Handle log dir dependency for Ranger KMS installation

> On Feb. 29, 2016, 3:15 p.m., Jonathan Hurley wrote: > > ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/setup_ranger_xml.py, > > lines 103-105 > > <https://reviews.apache.org/r/44060/diff/1/?file=1271897#file1271897line103> > >

Re: Review Request 44060: AMBARI-15199 : Handle log dir dependency for Ranger KMS installation

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/44060/#review121678 --- Ship it! Ship It! - Jonathan Hurley On Feb. 26, 2016, 7:43

Re: Review Request 43947: YARN restart icon appeared after 5 minutes after reconfig

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/43947/#review121676 --- Ship it! Ship It! - Jonathan Hurley On March 2, 2016, 12:02

Re: Review Request 43830: AMBARI-15127 : Add retry logic for DB Setup during Ranger upgrade step (to handle upgrade with Ranger HA)

<https://reviews.apache.org/r/43830/#comment183435> The other upgrade packs have downgrade scenarios too? Why not this one? - Jonathan Hurley On March 2, 2016, 8:36 a.m., Gautam Borad wrote: > > --- > This is an automatic

Re: Review Request 43947: YARN restart icon appeared after 5 minutes after reconfig

/Cluster.java (lines 412 - 416) <https://reviews.apache.org/r/43947/#comment183427> If we keep this approach, let's change the boolean to be less implementation dependant. Instead of `useClusterDao` it could be more generic like `bypassCache` - Jonathan Hurley On March 2, 2016, 10:

Re: Review Request 44264: Upgrade Warning on Non-Versioned Components

see the relationship between the two. - Jonathan Hurley On March 2, 2016, 6:55 a.m., Dmitro Lisnichenko wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache

[jira] [Updated] (AMBARI-15253) Ambari upgrade fails if there is incorrect version in upgrade table

[ https://issues.apache.org/jira/browse/AMBARI-15253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley updated AMBARI-15253: - Attachment: AMBARI-15253.patch > Ambari upgrade fails if there is incorrect vers

Re: Review Request 44264: Upgrade Warning on Non-Versioned Components

just ensuring that the stack listener sets the upgrade state to NONE. The problem reported was that, when upgrading, we were getting a warning on ZKFC b/c current != desired (both were UNKNOWN). I just want to make sure the problem reported is being fixed. - Jonathan Hurley On March 2, 2016

Re: Review Request 44228: Ambari upgrade fails if there is incorrect version in upgrade table

8489486 ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog220.java 2330a21 Diff: https://reviews.apache.org/r/44228/diff/ Testing --- Ran through an upgrade on the problem database. Unit tests pending. Thanks, Jonathan Hurley

Review Request 44228: Ambari upgrade fails if there is incorrect version in upgrade table

an upgrade on the problem database. Unit tests pending. Thanks, Jonathan Hurley

[jira] [Created] (AMBARI-15253) Ambari upgrade fails if there is incorrect version in upgrade table

Jonathan Hurley created AMBARI-15253: Summary: Ambari upgrade fails if there is incorrect version in upgrade table Key: AMBARI-15253 URL: https://issues.apache.org/jira/browse/AMBARI-15253

Re: Review Request 44188: Provide details on the JCE policy installed in the JVM used by Ambari

> On March 1, 2016, 2:08 p.m., Jonathan Hurley wrote: > > ambari-server/src/main/java/org/apache/ambari/server/controller/internal/RootServiceComponentResourceProvider.java, > > line 125 > > <https://reviews.apache.org/r/44188/diff/1/?file=1274878#file1274878line1

Re: Review Request 44188: Provide details on the JCE policy installed in the JVM used by Ambari

what's wrong :) - Jonathan Hurley On March 1, 2016, 11:26 a.m., Robert Levas wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://re

[jira] [Resolved] (AMBARI-15173) Express Upgrade Stuck At Manual Prompt Due To HRC Status Calculation Cache Problem

[ https://issues.apache.org/jira/browse/AMBARI-15173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley resolved AMBARI-15173. -- Resolution: Fixed > Express Upgrade Stuck At Manual Prompt Due To HRC Sta

[jira] [Reopened] (AMBARI-15173) Express Upgrade Stuck At Manual Prompt Due To HRC Status Calculation Cache Problem

[ https://issues.apache.org/jira/browse/AMBARI-15173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley reopened AMBARI-15173: -- > Express Upgrade Stuck At Manual Prompt Due To HRC Status Calculation Cache > P

Re: Review Request 43967: Express Upgrade Stuck At Manual Prompt Due To HRC Status Calculation Cache Problem

ode": 0, "host_name": "os-r6-mkqzcs-c10tom21unsecha-6.novalocal", "id": 754, "output_log": "output-754.txt", "request_id": 61, "role": "AMBARI_SERVER_ACTION", "stage_id": 1, "start_time": 1456227329191, "status": "HOLDING", "stderr": "", "stdout": "", "structured_out": {} } } ] } {code} Diffs (updated) - ambari-server/src/main/java/org/apache/ambari/server/orm/dao/HostRoleCommandDAO.java 14dac79 Diff: https://reviews.apache.org/r/43967/diff/ Testing --- Pending unit tests... Thanks, Jonathan Hurley

[jira] [Updated] (AMBARI-15058) Schema changes for component history

[ https://issues.apache.org/jira/browse/AMBARI-15058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley updated AMBARI-15058: - Attachment: AMBARI-15058.patch > Schema changes for component hist

[jira] [Updated] (AMBARI-15094) Patch Upgrade UpgradeCatalog Changes

[ https://issues.apache.org/jira/browse/AMBARI-15094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley updated AMBARI-15094: - Attachment: AMBARI-15094.patch > Patch Upgrade UpgradeCatalog Chan

[jira] [Updated] (AMBARI-15131) Create Component/Service Upgrade History On Finalize

[ https://issues.apache.org/jira/browse/AMBARI-15131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley updated AMBARI-15131: - Attachment: AMBARI-15131.patch > Create Component/Service Upgrade History On Final

[jira] [Updated] (AMBARI-15131) Create Component/Service Upgrade History On Finalize

[ https://issues.apache.org/jira/browse/AMBARI-15131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley updated AMBARI-15131: - Attachment: (was: AMBARI-15173.patch) > Create Component/Service Upgrade Hist

[jira] [Updated] (AMBARI-15131) Create Component/Service Upgrade History On Finalize

[ https://issues.apache.org/jira/browse/AMBARI-15131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley updated AMBARI-15131: - Attachment: AMBARI-15173.patch > Create Component/Service Upgrade History On Final

Re: Review Request 44060: AMBARI-15199 : Handle log dir dependency for Ranger KMS installation

/package/scripts/setup_ranger_xml.py (lines 103 - 105) <https://reviews.apache.org/r/44060/#comment182995> Could this be a security issue on systems where they only want specific users to access config directories? Granting a+rx? - Jonathan Hurley On Feb. 26, 2016, 7:43 a.m., Gautam

Re: Review Request 43967: Express Upgrade Stuck At Manual Prompt Due To HRC Status Calculation Cache Problem

ri/server/orm/AmbariJpaLocalTxnInterceptor.java b5442c2 ambari-server/src/main/java/org/apache/ambari/server/orm/TransactionalLocks.java 1768dd8 ambari-server/src/main/java/org/apache/ambari/server/orm/dao/HostRoleCommandDAO.java c2ded2f ambari-server/src/test/java/org/apache/ambari/annotations/LockAreaTest.java PRE-CREATION ambari-server/src/test/java/org/apache/ambari/annotations/TransactionalLockInterceptorTest.java 6ebdc0b ambari-server/src/test/java/org/apache/ambari/annotations/TransactionalLockTest.java 1862088 Diff: https://reviews.apache.org/r/43967/diff/ Testing --- Pending unit tests... Thanks, Jonathan Hurley

  1   2   3   4   5   6   7   8   9   10   >