Skip to content

Instantly share code, notes, and snippets.

View shivannakarthik's full-sized avatar

Karthik S shivannakarthik

View GitHub Profile
Capacity is assigned to the queues as min and max percentages of the parent in the hierarchy.
The minimum capacity is the amount of resources the queue should expect to have available to it if everything is running maxed out on the cluster.
The maximum capacity is an elastic like capacity that allows queues to make use of resources which are not being used to fill minimum capacity demand in other queues.
Children Queues inherit the resources of their parent queue
Minimum User Percentage and User Limit Factor are ways to control how resources get assigned to users within the queues they are utilizing.
The Min User Percentage is a soft limit on the smallest amount of resources a single user should get access to if they are requesting it.
User Limit Factor is a way to control the max amount of resources that a single user can consume.
#Installing Ranger Admin HA via Ambari causes a full cluster outage and the ambari wizard takes full control of the restarts.
#Below are the steps to enable HA manually wiht out having to use Ambari for setup.
1. Add Ranger Admin component to another host selected for HA in the cluster using Ambari API.
curl -u username:password -H "X-Requested-by:ambari" -i -k -X POST -d '{"host_components" : [{"HostRoles":{"component_name":"RANGER_ADMIN"}}]}' http://<ambari_host>:8080/api/v1/clusters/<clustername>/hosts?Hosts/host_name=<host_where_you_need_ha_component>
Note: Ambari API command used above puts Ranger Admin component on host. To install Ranger Admin component, go to Ambari --> Ranger --> Ranger Admin Host --> Click on drop down to re-install
Warning: Do not start Ranger Admin yet.
2. Setup loadbalancer for both Ranger Admins
@shivannakarthik
shivannakarthik / kub-monitor.screenrc
Created August 9, 2017 05:27 — forked from initcron/kub-monitor.screenrc
screen automation code to monitor kubernetes. use "screen -c kub-monitor.screenrc" to launch
screen watch -n 1 kubectl get pods
split
focus down
screen watch -n 1 kubectl get rc
split
focus down
screen watch -n 1 kubectl get deploy
split
focus down
screen watch -n 1 kubectl get replicasets
kubectl delete svc kubernetes-dashboard -n kube-system
kubectl apply -f https://gist.github.com/initcron/35c7cd7a7bd0c3d5df8ffafdd42d9d1c/raw/b8ef3903bbec75293d375cda0ec3f190c798f2b3/kube-dashboard-svc.yaml
@shivannakarthik
shivannakarthik / stack.yml
Created August 8, 2017 09:09 — forked from initcron/stack.yml
Docker Stack Deploy Configs
version: "3"
networks:
nw01:
driver: overlay
volumes:
db-data:
services:
@shivannakarthik
shivannakarthik / swarm_tutorial_v3.md
Created August 8, 2017 08:33 — forked from initcron/swarm_tutorial_v3.md
Docker Swarm with V3 stack specifications and stack deploy

Lab : Orchestrating and deploying app in Production with SWARM

Deploying Application Stack with Swarm Mode and Stack version "3" specification

Launch a Visualizer on Master (SWARM Manager)

docker run -itd -p 8080:8080 -v /var/run/docker.sock:/var/run/docker.sock schoolofdevops/visualizer
@shivannakarthik
shivannakarthik / setup_kubernetes_vagrant.md
Created August 8, 2017 05:36 — forked from initcron/setup_kubernetes_vagrant.md
Setting up Kubernetes Cluster on Ubuntu with Vagrant