Member since
09-29-2015
29
Posts
20
Kudos Received
10
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
1224 | 08-18-2016 07:51 PM | |
1830 | 08-18-2016 07:15 AM | |
17524 | 06-10-2016 04:20 PM | |
1096 | 06-10-2016 04:17 PM | |
3526 | 06-10-2016 02:27 PM |
01-10-2017
06:24 PM
1 Kudo
EMR is doing HBase on S3 with WAL stored on local HDFS - a better approach is to do WAL on EBS or EFS. WAL on local HDFS is not really recommended as you can loose data if the node goes away.
... View more
08-18-2016
07:51 PM
First of all the latest release which was using Docker on public clouds (AWS, GCP and Azure) was 1.2.3. The 1.3.0 or newer versions are not using Docker to run the Hadoop services. Anyway for 1.2.3 the answers are: 1. Containers were started with net=host, thus there was one container per VM - Docker was mostly used for packaging and distribution - thus every node had one container. You needed as many nodes as the size of the cluster was.
2. You can but the container was getting the full VM resources (see #1)
3. You need to install the Cloudbreak application (anywhere, that can be an EC2 instance for example but on-prem as well). The Cloudbreak application - note it's not the cluster - is composed of several micro-services, and these are running inside containers.
Can be GUI or CLI or API - every hostgroup can have different instance types, the cluster can be heteregenous. 4. http://sequenceiq.com/cloudbreak-docs/ 5. It depends on the number of nodes you'd like to provision. There are no additional costs on top of EC price thus yo ucan do a fairly easy math - multiply the number of nodes you think your cluster will have with the number of hours ... In Cloudbreak you can fully track usage costs on the Accounts tab.
... View more
08-18-2016
07:15 AM
1 Kudo
Salut Constantin
Currently this is tech preview due to some limitations - there are some changes undergoing within Mesos (unified containerizes, IP per container, reverse lookups, storage drivers, etc to name a few) - so expect a large change here.
Nevertheless if someone is happy with the current limitations (namely running with net=host) the code is stable and works well (we and a few others have test/dev clusters).
Should you want more details drop me a mail. Janos
... View more
08-17-2016
07:05 PM
1 Kudo
http://sequenceiq.com/cloudbreak-docs/latest/mesos/
... View more
06-13-2016
03:38 PM
It seams like your account does not have right to create a VPC (you can check this on AWS console where you can try to create a new VPC). Alternatively you can reuse your company's VPC as well - http://sequenceiq.com/cloudbreak-docs/latest/aws/#infrastructure-templates and check Create a new subnet in an existing VPC or Use an existing subnet in an existing VPC.
... View more
06-10-2016
06:12 PM
It's not so easy to read over the formatting but apparently a few containers did not start for you (e.g. uaadb, pcdb, cbdb). Can you do a cbd kill and after a cbd regenerate a cbd start. You should have 12 containers (microservices) and among those the databases.
... View more
06-10-2016
04:26 PM
1 Kudo
For a size like this is fine - you can check these Ansible scripts in order to set up an OpenStack, than use Cloudbreak.
... View more
06-10-2016
04:20 PM
Hi guys. This is due to an old SQL driver - as stated above you can either change the driver or wait until the next release where the driver will be updated. Sorry for the inconvenience.
... View more
06-10-2016
04:17 PM
The container should not be updated - you mean to say the docker version? Contiamners can be updated with docker pull but you should not be concerned as an end user or operator about this.
Did you face some issues or is this an observation?
... View more
06-10-2016
04:09 PM
Can you please SSH to the box and run docker ps and send us the results. Also can you check if you see any exceptions in cbd logs cloudbreak ?
... View more