rhoml

TL;DR

My team is looking for a site reliability engineer passionate about observability and reliability.

We are the team responsible for Platform and Site Reliability at Apptio, building our Kubernetes platform in AWS (EC2), including a bunch of leading-edge technology services around it to reduce the friction for our development teams.

In a typical day on this role, you will interact with Golang, Jsonnet, Kubernetes, Puppet, GitLab CI, Docker, Confluence, Jira, Slack, and AWS.

Don't worry if you don't know all these names/acronyms; we are not expecting you to, technology moves very fast these days.

rhoml

Next Steps

• Measure time spend on index, flush, refresh, merge, query, etc. (TD - done)
• Take hot threads snapshots under read+write, read-only, write-only (TD - done)
• Adjust refresh time to 10s (from 1s) and see how load changes (TD)
• Measure time of a rolling restart doing disable_flush and disable_recovery (TD)
• Specify routing on query -- make it choose same node for each shard each time (MD)
• GC new generation size (TD)
• Warmers

• measure before/after of client query time with and without warmers (MD)

rhoml

# Logstash Configuration for Mesos Masters and Slaves
input {
  file { 
    path => "/var/log/mesos/mesos-master.[EIFW]*"
    tags => [
      "master"
    ]
  }

  file { 

rhoml

require 'facter'
require 'json'

if Facter.value("ec2_instance_id") != nil
 instance_id = Facter.value("ec2_instance_id")
 region = Facter.value("ec2_placement_availability_zone")[0..-2]
 tags = Facter::Util::Resolution.exec("aws ec2 describe-tags --filters \"name=resource-id,values=#{instance_id}\" --region #{region} | jq '[.Tags[] | {key: .Key, value: .Value}]'")
 
 parsed_tags = JSON.parse(tags)
 parsed_tags.each do |tag|

rhoml

Keybase proof

I hereby claim:

• I am rhoml on github.
• I am rhoml (https://keybase.io/rhoml) on keybase.
• I have a public key whose fingerprint is 4289 50B6 1986 2303 5CE5 65EF 4D86 1C8B B81D C778

To claim this, I am signing this object:

rhoml

Gist Clients

Want to create a Gist from your editor, the command line, or the Services menu? Here's how.

Editor Support

• TextMate
• Emacs
• Vim
• Coda

rhoml

#!/bin/bash
# Simple reconfigure script to modify multiple nutcracker(twemproxy) servers in case of Redis 
# Failover.

export PATH=/sbin:/usr/local/bin:$PATH

NAME=sentinel
LOGFILE=/opt/sentinel/logs/reconfigure.log
ERRORLOGFILE=/opt/sentinel/logs/reconfigure.error.log
NUTCRACKER_CONF=/opt/nutcracker/etc/nutcracker.yml

rhoml

#!/bin/bash
export PATH=/sbin:/usr/local/bin:$PATH

NAME=sentinel
LOGFILE=/opt/sentinel/logs/reconfigure.log
ERRORLOGFILE=/opt/sentinel/logs/reconfigure.error.log
NUTCRACKER_CONF=/opt/nutcracker/etc/nutcracker.yml
NUTCRACKERFAILOVER_CONF=/opt/nutcracker/etc/nutcrackerfailover.yml
NUTCRACKER_PORTs='22121,22123'
MASTER_NAME=$1

rhoml

// Use Gists to store code you would like to remember later on
console.log(window); // log the "window" object to the console

rhoml

#!/bin/bash
# <master-name> <role> <state> <from-ip> <from-port> <to-ip> <to-port>
export PATH=/sbin:/usr/local/bin:$PATH
NUTCRACKER_CONF='/opt/nutcracker/conf/nutcracker.yml'
NUTCRACKER_PORT=22121
MASTER_NAME=$1
ROLE=$2
STATE=$3
FROM_IP=$4
FROM_PORT=$5