pmanvi

export JAVA_HOME=$(/usr/libexec/java_home)
export GRADLE_HOME=/opt/gradle
export M2_HOME=/opt/maven
export M2=$M2_HOME/bin
export PATH=$M2:$PATH:$GRADLE_HOME/bin

export MYSQL_HOME=/usr/local/bin/mysql
export PATH=$PATH:$MYSQL_HOME/bin
alias ll="ls -lptr"
alias cd..="cd .."

pmanvi

Production is awesome place to learn and know about the system. Team should feel lucky to work on those systems.

Make sure to have these parameters defined 
-XX:+HeapDumpOnOutOfMemoryError
-XX:HeapDumpPath=<path>

lets say that you are experiencing OOM, but you still don't determine the root cause of the issue, 
You might probably need to restart as soon as you see performance issues or even better daily thats perfectly fine & taking heap
dump will not practical. try to take heap dumpl.

pmanvi

import java.util.Arrays;
import java.util.HashMap;
import java.util.Map;
import java.util.Properties;

import org.apache.kafka.clients.consumer.KafkaConsumer;
import org.apache.kafka.clients.consumer.OffsetAndMetadata;
import org.apache.kafka.common.TopicPartition;
import org.apache.kafka.common.serialization.StringDeserializer;
import org.zeroturnaround.exec.ProcessExecutor;

pmanvi

// Lets keep only last 10 builds
MAX_BUILDS = 10 
 
def jobs = Jenkins.instance.items;
println "Total Jobs" + jobs.size()

for (job in jobs) {
    println "Job: " + job.name
    try {
        if(job instanceof jenkins.branch.MultiBranchProject) {

pmanvi

import redis
import time
import random


def load_file(fp, fpKey, r, expiry):
    with open(fp, "rb") as f:
        data = f.read()
    p = r.pipeline()
    p.set(fpKey, data)