[GitHub] bigtop pull request #343: BIGTOP-3001. Change uid and gid for jenkins user i...
GitHub user aajisaka opened a pull request: https://github.com/apache/bigtop/pull/343 BIGTOP-3001. Change uid and gid for jenkins user in bigtop-toolchain https://issues.apache.org/jira/browse/BIGTOP-3001 You can merge this pull request into a Git repository by running: $ git pull https://github.com/aajisaka/bigtop BIGTOP-3001 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/bigtop/pull/343.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #343 commit 9049aa0f3fc40fc755c5798cb322014ed0701bf6 Author: Akira Ajisaka Date: 2018-02-27T10:01:29Z BIGTOP-3001. Change uid and gid for jenkins user in bigtop-toolchain ---
[jira] [Created] (BIGTOP-3007) expose hive config options for zookeeper
James Beedy created BIGTOP-3007: --- Summary: expose hive config options for zookeeper Key: BIGTOP-3007 URL: https://issues.apache.org/jira/browse/BIGTOP-3007 Project: Bigtop Issue Type: New Feature Components: hive Environment: \ Reporter: James Beedy Support for config properties "hive.support.concurrency" and "hive.zookeeper.quorum" in hive config xml. Need capability to configure hiveserver2 lock table per https://www.cloudera.com/documentation/cdh/5-0-x/CDH5-Installation-Guide/cdh5ig_hiveserver2_configure.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] bigtop pull request #344: BIGTOP-3007
GitHub user jamesbeedy opened a pull request: https://github.com/apache/bigtop/pull/344 BIGTOP-3007 In support of hiveserver2 table lock, hive config needs to expose the properties: * hive.support.concurrency * hive.zookeeper.quorum Added hive.zookeeper.quorum and hive.support.concurrency in support of hiveserver2 table lock. Add vars to init.pp. Add zookeeper interface and corresponding reactive bits. Modified install function in lib to facilitate zk_hosts. Update deployment_matrix. You can merge this pull request into a Git repository by running: $ git pull https://github.com/jamesbeedy/bigtop hive_config_add_zookeeper Alternatively you can review and apply these changes as the patch at: https://github.com/apache/bigtop/pull/344.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #344 commit 8e7350573ff8500fd7b68a3902421e4ee601a22b Author: jamesbeedy Date: 2018-02-27T17:19:06Z Add hive configuration properties in support of hiveserver2 In support of hiveserver2 table lock, hive config needs to expose the properties: * hive.support.concurrency * hive.zookeeper.quorum Added hive.zookeeper.quorum and hive.support.concurrency in support of hiveserver2 table lock. Add vars to init.pp. Add zookeeper interface and corresponding reactive bits. Modified install function in lib to facilitate zk_hosts. Update deployment_matrix. ---
[GitHub] bigtop pull request #343: BIGTOP-3001. Change uid and gid for jenkins user i...
Github user asfgit closed the pull request at: https://github.com/apache/bigtop/pull/343 ---
Something weird is going on with our puppet
Guys, I am trying to run the following command: puppet apply -d --modulepath=bigtop-deploy/puppet/modules:/etc/puppet/modules bigtop-deploy/puppet/manifests/site.pp from the top-level directory of Bigtop source tree. to deploy some cluster configuration in a container. All I am getting though is this error message: Debug: Caching environment 'production' (ttl = 0 sec) Error: Could not find class jdk for c41f94213de4 on node c41f94213de4 Looks like class jdk under bigtop-deploy/puppet/manifests could not be found. The latest change related to this has happened in hash 40e796b (made by Kevin), but I am kinda sure I was able to deploy cluster after that. Did something got changed which I missed and their new rules of using the recipes? Thanks for any leads! -- With regards, Konstantin (Cos) Boudnik 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622 Disclaimer: Opinions expressed in this email are those of the author, and do not necessarily represent the views of any company the author might be affiliated with at the moment of writing.
