Posts

Showing posts with the label DEVOPS

Part 2 Series of Elasticsearch Cluster on Spot Instances with zero downtime in App?

Image
Elasticsearch Data node setup : Data node are the nodes/instance where our index data will reside.There is two things to consider for data nodes while creating an index i.e 1.Number of shards: How to divide our index data into number of shards so that data can be retrieved in fast paced manner. It help in sharding data to different nodes so that we can scale it well. 2.Number of Replicas: Number of Copies of primary shards are called number of replicas Let’s take an example to understand it’s concept : How many node failure can be possible if we have 3 node data cluster with 5 shards and 1 replica. Elasticsearch notes: Primary shards and its replica will not be on same node. If we delete one node from our cluster then : Our cluster will re-balance our lost replicas and move to existing nodes ,for time-being the cluster becomes yellow as you can see below for unassigned shards. Once rebalancing is completed our cluster back to green state...

What is a Devops ??

What is Devops and its culture to adopt? Devops is simply a means of collaboration between developers and operations team working together over a common goal of making a commit change or complete source code live with just click of an instance i.e How operations team with the help of their coding skill sets automate their infrastructure in an cost efficient and effective manner in order to save time to market the product in fastest possible way. Devops Best Practices:(AWS Specific)    1.Do not stick with any single tool or code for solving a problem whether it can be Backup and restore or monitoring,cloud infrastructure setup ,first solve the problem then provide the best way of doing it with a purpose like for monitoring we can use any tool like nagios or zabbix but both tools has its own advantages and disadvantages so before moving with any tools it better to understand its pros and cons. 2.Always Keep your App server,DB server in private subnet so no public acces...