You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Thiru (JIRA)" <ji...@apache.org> on 2015/10/14 08:14:06 UTC
[jira] [Commented] (AMBARI-7504) Ambari support for Windows
platform
[ https://issues.apache.org/jira/browse/AMBARI-7504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14956337#comment-14956337 ]
Thiru commented on AMBARI-7504:
-------------------------------
Hi ,
I had installed ambari server "ambari-scom-1.5.1.2.0.0.0-673" in windows server 2012. also created database "HadoopMetrics" in MSSQL server2012. gone through this URL "https://cwiki.apache.org/confluence/display/AMBARI/2.+Installation" to install and configure the ambari server successfully. after starting server, I am executing this "http://172.24.112.55:8080/api/v1/clusters" and am getting the following error "Local Exception Stack:
Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.4.0.v20120608-r11652): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLSyntaxErrorException: 'ALTER TABLE' cannot be performed on 'CLUSTERCONFIG' because it does not exist.
Error Code: 30000
Call: ALTER TABLE clusterconfig DROP CONSTRAINT clstrconfigclstrid
Query: DataModifyQuery(sql="ALTER TABLE clusterconfig DROP CONSTRAINT clstrconfigclstrid")"
so please anyone to help me to resolve this issue.
-Thiru.
> Ambari support for Windows platform
> -----------------------------------
>
> Key: AMBARI-7504
> URL: https://issues.apache.org/jira/browse/AMBARI-7504
> Project: Ambari
> Issue Type: Epic
> Components: ambari-agent, ambari-server, ambari-web
> Affects Versions: 2.0.0
> Environment: Windows
> Reporter: Jayush Luniya
> Assignee: Jayush Luniya
> Fix For: 2.1.0
>
>
> The purpose of this umbrella JIRA is to enable Ambari on Windows support so as to enable provisioning/managing and monitoring of Hadoop clusters on Windows. The work will be divided into two phases as outlined below.
> *Software Requirements*
> - Windows Server 2008, Windows Server 2012, Windows Server 2012 R2
> - Python x64 (2.6 or later)
> - Python pywin32 Extensions
> - Python WMI module
> - Microsoft Visual C++ 2010 Redistributable Package (64-bit)
> - Microsoft .NET Framework 4.0
> - Java JDK 7, OpenJDK7
> - Visual Studio 2008 x64 redistributable package
> - OpenSSL
> - JDBC Driver for MS SQL Server
> - MS SQL Server
> *Setup*
> - Enable Ambari-Server and Ambari-Agent, Ambari-Web support on Windows
> - Ambari Server and Ambari Agent will be packaged as MSIs.
> - Ambari Server Setup
> Phase 1: Focus on setup + start. No advanced configurations.
> Phase 2: Advanced configuration options (LDAP/AD auth, HTTPS, encryption).
> - Bootstrapping Agents
> Phase 1: In Linux, agent is pushed by the server to all the hosts using SSH. In phase 1, we will not support automatic bootstrapping of agents and will require manual installation of ambari agents on all hosts.
> Phase 2: To enable automatic bootstrapping of agents, we will leverage powershell remoting.
> *Database*
> - Ambari Server DB --- Use existing SQL Server
> - Hive, Oozie --- Use existing SQL Server
> - MetricsSink (Phase 1) --- Use existing SQL Server
> *Provisioning*
> - Ambari should support deploying Hadoop cluster on Windows through Ambari REST API as well as Ambari Web portal.
> - Ambari should automatically install Windows Hadoop MSI on all hosts.
> *Managing*
> - Ambari should support managing and monitoring hosts, services and host components.
> - Add/Delete services
> - Add/Delete hosts
> - Run service checks
> - Start/Stop/Restart/Rolling Restart services and service components on a host.
> - Enable/disable Maintenance mode.
> - Configs and Config Groups
> *Metrics*
> - Phase 1: Reuse Metrics Sink package from Ambari SCOM project. In phase 1, we will only report service-level metrics. https://cwiki.apache.org/confluence/display/AMBARI/2.+Installation
> - Phase 2: Integrate new metrics service proposed in AMBARI-5707. In phase 2, we will enable both service-level and host-level metrics.
> *Alerts*
> - Phase 1: In phase 1, we won’t add support for alerts.
> - Phase 2: Integrate new alerting service proposed in AMBARI-6354
> *Security*
> - Phase 1: In phase 1, we won't add support for security scenarios.
> - Phase 2: Add support for security scenarios. Details are being flushed out and the Epic will be updated with security scenarios.
> *Upgrade*
> - Phase 1: In phase 1, we won't add support for Ambari upgrade and HDP stack upgrade.
> - Phase 2: In phase 2, we will add support for Ambari upgrade and HDP stack upgrade.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)