As ambari comes under cloudera now, what is the price per hour of the enterprise edition of apache ambari
#asukwal9 - Ambari is no longer a part of Cloudera enterprise support and there was never a per hour consumption for Ambari or HDP (Hortonworks Data Platform). Enterprise licensing was node based not consumption based. Today enterprise level support for these services around Ambari is End of Life unless there is an exception. Existing licensed HDP customers are migrating to CDP (Cloudera Data Platform).
Related
I am planning to update LDAP OpenDJ 2.6.4 version to OpenDJ 4.4.11 version. Is there any recommended way to migrate the data to the new OpenDJ 4.4.11 LDAP server with minimalistic downtime?
The expectation is to migrate the data records to OpenDJ 4.4.11 version, with minimum downtime.
OpenDJ supports replication of data between servers of different versions.
And it also supports easy upgrade from version 2 to version 4.
If you have setup high availability through replicated servers, you should be able to upgrade with no downtime of the service.
I'm trying to perform an upgrade on an environments 2 OpenDJ directory servers with 1 standalone replication server between them referring to the 3.5 Upgrade doc. However, I could not find information on the order of upgrade for replication topology with standalone replication server. Should we go with upgrade of Directory servers first followed by replication, or vice versa. Can upgrade script identify between replication and directory servers.
It doesn't matter, replication is compatible between versions.
I can't understand for difference between Apache Ignite and GridGain platform. They are equals? Or GridGain is a standard that implemented by Apache Ignite?
From the website:
Apache® Ignite™ was originally contributed to the Apache Software Foundation by GridGain Systems. The project rapidly evolved into a top level Apache project with tens of thousands of downloads per month. The GridGain Professional Edition, Enterprise Edition, and Ultimate Edition are built on Apache Ignite.
Enterprise and Ultimate editions have some "enterprise" features that are not in the open source version.
Indeed, Gridgain is wraper built on top of Ignite.
Gridgain gives you additional features such as Security, Rolling production update etc that is required for enterprise level application.
you may find the full list here
https://www.gridgain.com/products/gridgain-vs-ignite
How to use Windows Server 2012 and 2008 as an AWS instanace in free tier account? I am having free tier account on AWS, so can I use Windows Server as my instance?
From AWS Free Usage Tier:
AWS Free Tier (Per Month):
Elastic Compute Cloud (EC2)
750 hours of Amazon EC2 Linux t2.micro instance usage (1 GiB of memory and 32-bit and 64-bit platform support) – enough hours to run continuously each month
750 hours of Amazon EC2 Microsoft Windows Server t2.micro instance usage (1 GiB of memory and 32-bit and 64-bit platform support) – enough hours to run continuously each month
Note that the restriction is on the instance type -- it needs to be a t2.micro instance (but possibly also includes the older t1.micro).
When launching an Amazon EC2 instance, select an Amazon Machine Image (AMI) that says "Free tier eligible". This currently includes:
Microsoft Windows Server 2012 Base
Microsoft Windows Server 2008 R2 Base
Microsoft Windows Server 2003 R2 Base
I wanted to broach the issue of SQL Server's Hadoop distribution called HDInsight.
Given that there is a connection provided to Hadoop, does anyone have experience with HDInsight and particularly a comparison between the Hadoop / SQL Server connector and HDIinsight / SQL Server from a real life DTP scenario or personal 1 node installation?
http://sqlmag.com/blog/use-ssis-etl-hadoop
http://www.microsoft.com/en-us/download/details.aspx?id=27584
http://www.microsoft.com/en-us/sqlserver/solutions-technologies/business-intelligence/big-data.aspx
HDInsight is the distribution of Hadoop that Microsoft maintains for use in Azure. You could roughly compare this to Amazon Elastic MapReduce. They both serve the purpose of being a hosted Hadoop service that has almost no management overhead.
The Hortonworks Data Platform for Windows contains the open source changes that Hortonworks and Microsoft have collaborated on to make Hadoop run well on Windows. HDP isn't HDInsight.
In short - you don't need to use HDInsight if you want to run Hadoop in a Windows environment.
While I can't speak directly to using HDInsight and moving data back and forth between SQL Server, I've done implemented a data processing solution using SQL Server, Hadoop, and Elastic MapReduce. Barring some data quality issues and BULK INSERT weirdness, the process was painless.
Finally, you ask "do we really want to run Hadoop size datasets on Windows servers?" - Windows performs well and has solid tooling around it. I've been somewhat skeptical about running Hadoop and other Java platform software on Windows because of legacy Java I/O issues and a lack of community support, not because of any performance issues.
The largest issues that Windows companies will find moving to Hadoop is there will be limited support in community forums and channels when the problem becomes a Hadoop + Windows issue. It's very easy for people to throw their hands up and say "Nope, not helping out, don't have Windows." With time and adoption, this problem goes away. Besides, nothing says you have to finish on the same platform you start with. You could easily deploy with HDP on Windows and move to HDP on Linux at a later date.
I have put together some SQL Server and Hadoop basics for DBAs that should be helpful.