I tried to create two Memcache cluster's in Elastic Cache Using Elastic Beanstalk in AWS. Both got stuck in the same state saying 'creating' for the past 3 hrs.
Any help will be appreciated.
I also faced the same issue yesterday while creating 2 Redis clusters using terraform at the same time.
It got resolved when created one more Redis cluster in the same region using AWS console.
Note: There seems to be an issue with creating multiple Custers at the same time the same region/AZ.
Related
I have a Openshift Cluster setup in which I have aggregated Openshift logging.
Elasticsearch , fluentd and Kibana.
I have setup external elastic search on different server. I want to forward my Openshift cluster logs to my newly setup Elasticsearch.
Please help me in resolving this.
Thanks
I believe what you need is explained in https://docs.openshift.com/container-platform/3.11/install_config/aggregate_logging.html#sending-logs-to-an-external-elasticsearch-instance
From your question it's not clear what problem you are facing.
I am trying to setup multiple instance of couchbase (couchbase-server-enterprise-4.5.0-DP1-centos7.x86_64.rpm)in fedora OS 21 .
I am following the steps in the below URL to setup the multiple instances of couchdb.
[http://docs.couchbase.com/admin/admin/Install/rhel-multiple-instances.html][1]
I have completed the first steps and able to launch couchbase in the http://localhost:8091/ui/index.html.
I have installed couchbase only once. Is it fine or do I need to install one more instance.
I am not sure how to proceed from step 2 onwards.
If I don't create any user defined ports in /opt/couchbase/etc/couchbase/static_config, will it be a problem?
I have setup nofile parameter as below in /etc/security/limits.conf file as mentioned in step 2.
Also, in the step 4 it is mentioned that, there is only one /opt/couchbase/etc/couchbase/static_config file. How can I setp different short_name parameter in that file.
How , once instance of couchbase identifies another instance of couchbase?
Couchbase really is much happier, and you will be too, to be on it's own OS, even if it is in something like Docker, VMs, etc. So I strongly recommend that you get something like Docker or VirtualBox to play with. Getting Couchbase to run multiple instances on the same OS is just not worth the hassle given the ease of other tools like I already mentioned.
That said, for development purposes, one of the best things about Couchbase is that you can develop on one node of Couchbase, but deploy against a much larger production cluster even with Multi-Dimensional Scaling enabled. It works very very well.
I have a Python project that requires the installation and compilation of quite a few dependencies that can easily take 10-15 minutes.
If I were to use Elastic Beanstalk and auto scaling would that mean that each EC2 instance would take 10-15 minutes to boot, or does EB do more intelligent snapshotting/cloning?
Would I see much better boot up times by pre-baking AMIs?
Yes, it is a good idea to have fast boot up times. Elastic Beanstalk will work with custom AMIs. Its also a good idea because if your dependencies are out of service, you won't be able to start new servers. Happened to me before :(.
I'm new to GCE and want to migrate my web site there. I created a VM instance group hoping. I installed all the packages and set it up a couple days ago. But today I noticed my VM instance group has a different name (postfix, to be exact), and the disk is flushed empty. Is it possible to restore its status, or at least make sure it won't get wiped out again? I'm so surprised that GCE wiped out everything and I wonder if I'm missing something during setup.
A few details in case they are related:
I'm using a trusty image for the VM.
The cloud storage is chosen to be a regular persistent disk.
It was working with emphemeral IP, and yesterday I started to use Cloud DNS to host my domain. I should have used a static IP, but that mistake shouldn't cause the VM instance group to be flushed...
I'm using cloud sql as the database service.
Maybe I should just use VM instance, given I don't have much traffic now?
Any help will be greatly appreciated~
Any good resource on how to port a LAMP stack to Ec2?
Mainly I'm concerned about storage, the MySQL part. The existing app works agains a single store. Do I need to port all my storage to S3? Will the EC2 instances be able to share a single MySQL database? Alternatively I can partition my data and have a single database for each EC2 image, but I still need a global user account database for authentication and if the data is partitioned the requests have to be routed to the proper image. Not sure how this is achieved in EC2.
To wrap up: where should I start?
These Tips for deploying a LAMP stack on Amazon EC2 are IMO a really good starting point. I'd suggest to read them first (I'm not sure I understand your concerns about the storage part), maybe things will be clearer after.
I know this is old, but for anyone who's in this situation check out: http://www.robotmedia.net/2011/04/how-to-create-an-amazon-ec2-instance-with-apache-php-and-mysql-lamp/
That is the most straight forward tutorial I've found for implementing a LAMP stack on Amazon EC2.
Using S3 isn't required, although it is an affordable way to host files. Yes, multiple instances can share a single database and you can use database replication for additional availability. Here's a great tutorial for that: http://aciddrop.com/2008/01/10/step-by-step-how-to-setup-mysql-database-replication/