diff --git a/2026/day-02/linux-architecture-notes.md b/2026/day-02/linux-architecture-notes.md new file mode 100644 index 0000000000..19212c725b --- /dev/null +++ b/2026/day-02/linux-architecture-notes.md @@ -0,0 +1,88 @@ +# Linux Architecture, Processes, and systemd + +## 1. Core Components of Linux + +### Kernel (known as "Linux Kernel") +- The **core of the OS**(Heart) +- Manages: + - CPU scheduling + - Memory management + - Hardware access (drivers) + - Process lifecycle +- Runs in **kernel space** (full privileges) + +### User Space +- Where **applications and users** operate +- Includes: + - Shells (bash, zsh) + - Utilities (`ls`, `ps`, `top`) + - Services (nginx, docker) +- Cannot access hardware directly → requests go via kernel + +### Init System (systemd) +- First process started by the kernel (**PID 1**) +- Responsible for: + - Starting services + - Restarting failed services + - Managing logs and dependencies + +--- + +## 2. How Processes Work in Linux + +### Process Creation +- A new process is created using: + - `fork()` → creates a copy + - `exec()` → loads a new program +- Every process has: + - **PID** (Process ID) + - **PPID** (Parent PID) + - Owner (user) + +### Process States +- **R (Running)** – Executing on CPU +- **S (Sleeping)** – Waiting for I/O or event +- **D (Uninterruptible Sleep)** – Waiting for disk/network (cannot be killed) +- **T (Stopped)** – Paused (e.g., Ctrl+Z) +- **Z (Zombie)** – Finished execution but parent hasn’t cleaned it up + +> Zombies don’t use CPU/memory, but many zombies indicate a bug. + +--- + +## 3. What systemd Does (and Why It Matters) + +- Controls system services using **units** +- Common unit types: + - `service` – background services + - `timer` – cron replacement + - `target` – system states (multi-user, graphical) + +### Why systemd is Important +- Automatically restarts crashed services +- Handles service dependencies +- Centralized logging with `journalctl` +- Faster boot and better observability + +--- + +## 4. Daily Linux Commands (DevOps Essentials) + +1. `ps aux` – View running processes +2. `top` / `htop` – Monitor CPU & memory usage +3. `systemctl status ` – Check service health +4. `journalctl -u ` – View service logs +5. `kill -9 ` – Force stop a stuck process + +--- + +## 5. DevOps Takeaway + +- Kernel = control +- Processes = workload +- systemd = reliability + +If you understand these three: +- You can debug crashes +- Fix performance issues +- Confidently manage production servers diff --git a/2026/day-03/linux-commands-cheatsheet.md b/2026/day-03/linux-commands-cheatsheet.md new file mode 100644 index 0000000000..37a7b548b8 --- /dev/null +++ b/2026/day-03/linux-commands-cheatsheet.md @@ -0,0 +1,161 @@ +# Linux Commands Cheat Sheet +**DevOps Essential Command Toolkit** + +-- +## 📊 Process Management + +| Command | Usage | +|---------|-------| +| `ps aux` | Display all running processes with detailed info | +| `top` | Real-time process monitoring and system stats | +| `htop` | Interactive process viewer (better than top) | +| `kill ` | Terminate process by Process ID | +| `kill -9 ` | Force kill a process (SIGKILL) | +| `killall ` | Kill all processes by name | +| `pgrep ` | Find process ID by name | +| `bg` | Resume suspended job in background | +| `fg` | Bring background job to foreground | +| `jobs` | List all background jobs | +| `nohup &` | Run command immune to hangups | +| `systemctl status ` | Check service status | +| `systemctl start ` | Start a service | +| `systemctl stop ` | Stop a service | +| `systemctl restart ` | Restart a service | + +--- + +## 📁 File System Commands + +| Command | Usage | +|---------|-------| +| `df -h` | Show disk usage in human-readable format | +| `du -sh ` | Show directory size summary | +| `ls -lah` | List files with hidden items and human-readable sizes | +| `find / -name ` | Search for file by name from root | +| `find . -type f -size +100M` | Find files larger than 100MB | +| `tail -f ` | Follow log file in real-time | +| `tail -n 50 ` | Display last 50 lines of file | +| `head -n 20 ` | Display first 20 lines of file | +| `grep -r "error" /var/log/` | Search for "error" recursively in logs | +| `chmod 755 ` | Change file permissions (rwxr-xr-x) | +| `chown user:group ` | Change file ownership | +| `ln -s ` | Create symbolic link | +| `tar -czf archive.tar.gz ` | Create compressed archive | +| `tar -xzf archive.tar.gz` | Extract compressed archive | +| `mount /dev/sdb1 /mnt` | Mount a disk partition | + +--- + +## 🌐 Networking & Troubleshooting + +| Command | Usage | +|---------|-------| +| `ping ` | Test connectivity to host | +| `ip addr` | Show all network interfaces and IP addresses | +| `ip route` | Display routing table | +| `curl ` | Transfer data from/to servers | +| `curl -I ` | Fetch HTTP headers only | +| `wget ` | Download files from web | +| `netstat -tulpn` | Show listening ports and services | +| `ss -tulpn` | Modern alternative to netstat | +| `dig ` | DNS lookup and query details | +| `nslookup ` | Query DNS name servers | +| `traceroute ` | Trace packet route to destination | +| `ifconfig` | Display/configure network interfaces (legacy) | +| `tcpdump -i eth0` | Capture network packets on interface | +| `iptables -L` | List firewall rules | +| `hostname -I` | Show all IP addresses of host | + +--- + +## 🔍 System Information + +| Command | Usage | +|---------|-------| +| `uname -a` | Display system information | +| `uptime` | Show system uptime and load average | +| `free -h` | Display memory usage in human-readable format | +| `lsblk` | List block devices (disks and partitions) | +| `lscpu` | Display CPU architecture information | +| `vmstat` | Report virtual memory statistics | + +--- + +## 📝 Log Analysis Quick Commands + +```bash +# Check system logs +journalctl -xe # Recent logs with explanations +journalctl -u nginx.service # Logs for specific service +journalctl --since "1 hour ago" # Logs from last hour + +# Apache/Nginx logs +tail -f /var/log/nginx/error.log +tail -f /var/log/apache2/access.log + +# System logs +tail -f /var/log/syslog +grep -i "error" /var/log/syslog | tail -20 +``` + +--- + +## 🚨 Emergency Troubleshooting Workflow + +```bash +# 1. Check system resources +top # CPU and memory +df -h # Disk space +free -h # Memory + +# 2. Check service status +systemctl status +journalctl -u -n 50 + +# 3. Check network +ip addr # IP configuration +ss -tulpn # Open ports +ping 8.8.8.8 # External connectivity + +# 4. Check logs +tail -f /var/log/syslog +grep -i error /var/log/syslog +``` + +--- + +## 💡 Pro Tips + +- Use `Ctrl + R` for reverse search in command history +- Combine commands with `|` (pipe) for powerful workflows +- Use `&&` to chain commands (runs second only if first succeeds) +- Press `Tab` for auto-completion +- Use `man ` to read manual pages +- Add `| less` to paginate long outputs +- Use `watch -n 2 ` to run command every 2 seconds + +--- + +## 🎯 Common Real-World Scenarios + +**Scenario 1: Server running slow** +```bash +top # Check CPU/memory +df -h # Check disk space +ps aux | grep # Find problematic process +``` + +**Scenario 2: Service not responding** +```bash +systemctl status # Check service status +journalctl -u -n 50 # Check recent logs +ss -tulpn | grep # Check if port is listening +``` + +**Scenario 3: Network connectivity issues** +```bash +ping 8.8.8.8 # Test internet +ip addr # Check IP config +dig google.com # Test DNS +traceroute # Find where packets drop +``` diff --git a/2026/day-04/linux-practice.md b/2026/day-04/linux-practice.md new file mode 100644 index 0000000000..60cd957498 --- /dev/null +++ b/2026/day-04/linux-practice.md @@ -0,0 +1,1107 @@ +# Linux Practice Log - Day 04 +**Hands-On Linux Command Practice** + +Date: February 08, 2026 +Environment: Ubuntu 24 Container + +--- + +## 🔍 Process Checks + +### 1. Display Running Processes (ps aux) + +**Command:** +```bash +ps aux | head -15 +``` + +**Output:** +``` +USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND +root 1 8.0 0.1 352336 17896 ? Ssl 06:19 0:00 /process_api --addr 0.0.0.0:2024 --max-ws-buffer-size 32768... +root 11 33.3 0.0 10848 3580 ? S 06:19 0:00 /bin/sh -c ps aux | head -15 +root 12 100 0.0 15996 8280 ? R 06:19 0:00 ps aux +root 13 0.0 0.0 10756 4184 ? S 06:19 0:00 head -15 +``` + +**What I Learned:** +- The first process (PID 1) is the main process running in this environment +- %CPU and %MEM columns show resource usage +- STAT column shows process state (S=sleeping, R=running, Ssl=session leader sleeping) +- VSZ = Virtual Memory, RSS = Resident Set Size (actual physical memory) + +--- + +### 2. Find Process by Name (pgrep) + +**Command:** +```bash +pgrep -a process +``` + +**Output:** +``` +1 /process_api --addr 0.0.0.0:2024 --max-ws-buffer-size 32768 --cpu-shares 1024... +``` + +**What I Learned:** +- `pgrep -a` shows both PID and full command +- Useful for quickly finding specific processes without parsing ps output +- Alternative to `ps aux | grep process` + +--- + +### 3. Process Hierarchy (ps -ef) + +**Command:** +```bash +ps -ef | grep -E "PID|process" | head -5 +``` + +**Output:** +``` +UID PID PPID C STIME TTY TIME CMD +root 1 0 2 06:19 ? 00:00:00 /process_api --addr 0.0.0.0:2024... +root 48 1 66 06:20 ? 00:00:00 /bin/sh -c ps -ef | grep... +``` + +**What I Learned:** +- PPID column shows parent process ID +- Process 1 has PPID 0 (it's the init process) +- Shows parent-child relationships clearly + +--- + +## 📊 System Resource Monitoring + +### 4. Real-Time System Overview (top) + +**Command:** +```bash +top -b -n 1 | head -20 +``` + +**Output:** +``` +top - 06:19:56 up 0 min, 0 user, load average: 0.00, 0.00, 0.00 +Tasks: 4 total, 1 running, 3 sleeping, 0 stopped, 0 zombie +%Cpu(s): 0.0 us, 0.0 sy, 0.0 ni, 100.0 id, 0.0 wa, 0.0 hi, 0.0 si +MiB Mem : 9216.0 total, 9200.5 free, 15.5 used, 8.6 buff/cache +MiB Swap: 0.0 total, 0.0 free, 0.0 used. 9200.5 avail Mem + + PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND + 1 root 20 0 352644 18452 0 S 0.0 0.2 0:00.37 process_api +``` + +**What I Learned:** +- Load average shows 1, 5, and 15-minute averages +- Memory breakdown: total, free, used, buff/cache +- No swap configured in this environment +- CPU is 100% idle (id) - system not under load +- `-b` flag runs top in batch mode (non-interactive) + +--- + +### 5. System Uptime + +**Command:** +```bash +uptime +``` + +**Output:** +``` + 06:20:13 up 0 min, 0 user, load average: 0.00, 0.00, 0.00 +``` + +**What I Learned:** +- Shows how long system has been running +- Load average indicates system load (0.00 means idle) +- User count shows active sessions + +--- + +## 💾 Disk and Memory Analysis + +### 6. Disk Space Usage (df -h) + +**Command:** +```bash +df -h +``` + +**Output:** +``` +Filesystem Size Used Avail Use% Mounted on +none 9.9G 2.1M 9.9G 1% / +none 315G 0 315G 0% /dev +none 315G 0 315G 0% /dev/shm +none 315G 0 315G 0% /sys/fs/cgroup +none 1.0P 0 1.0P 0% /mnt/transcripts +none 1.0P 0 1.0P 0% /mnt/skills/public +none 9.9G 2.1M 9.9G 1% /container_info.json +``` + +**What I Learned:** +- `-h` flag shows human-readable sizes (GB, MB, etc.) +- Root filesystem is 9.9GB with only 1% used +- Multiple mount points available +- Can quickly identify disk space issues + +--- + +### 7. Memory Usage (free -h) + +**Command:** +```bash +free -h +``` + +**Output:** +``` + total used free shared buff/cache available +Mem: 9.0Gi 13Mi 9.0Gi 0B 8.2Mi 9.0Gi +Swap: 0B 0B 0B +``` + +**What I Learned:** +- 9GB total memory, only 13MB used +- No swap space configured +- Buff/cache is minimal at 8.2MB +- `available` column shows memory available for new processes + +--- + +## 📝 Log Analysis + +### 8. System Boot Messages (dmesg) + +**Command:** +```bash +dmesg | tail -20 +``` + +**Output:** +``` +[ 0.000000] Starting gVisor... +[ 0.205956] Politicking the oom killer... +[ 0.420567] Segmenting fault lines... +[ 0.688076] Accelerating teletypewriter to 9600 baud... +[ 1.153015] Forking spaghetti code... +[ 1.533230] Creating bureaucratic processes... +[ 1.906427] Searching for needles in stacks... +[ 2.244173] Searching for socket adapter... +[ 2.366414] Feeding the init monster... +[ 2.776975] Creating process schedule... +[ 2.928509] Checking naughty and nice process list... +[ 3.353270] Ready! +``` + +**What I Learned:** +- `dmesg` shows kernel ring buffer messages +- Timestamps shown in seconds since boot +- Useful for hardware detection and kernel issues +- This system uses gVisor (lightweight container runtime) + +--- + +### 9. Checking Available Logs + +**Command:** +```bash +ls -lah /var/log/ | head -15 +``` + +**Output:** +``` +total 663K +drwxr-xr-x 5 root root 280 Nov 21 01:56 . +drwxr-xr-x 11 root root 260 Oct 13 14:09 .. +-rw-r--r-- 1 root root 20K Nov 21 01:59 alternatives.log +drwxr-xr-x 2 root root 100 Nov 21 01:59 apt +-rw-r--r-- 1 root root 60K Oct 13 14:03 bootstrap.log +-rw-rw---- 1 root utmp 0 Oct 13 14:02 btmp +-rw-r--r-- 1 root root 575K Nov 21 02:00 dpkg.log +-rw-r--r-- 1 root root 0 Oct 13 14:03 faillog +-rw-r--r-- 1 root root 5.1K Nov 21 01:59 fontconfig.log +drwxr-sr-x 2 root systemd-journal 40 Nov 21 01:55 journal +-rw-rw-r-- 1 root utmp 0 Oct 13 14:02 lastlog +``` + +**What I Learned:** +- Common log locations in /var/log/ +- `dpkg.log` tracks package installations +- `btmp` logs failed login attempts +- Different files have different permissions (security) + +--- + +### 10. Package Management Logs + +**Command:** +```bash +tail -20 /var/log/dpkg.log +``` + +**Output:** +``` +2025-11-21 01:59:15 configure gstreamer1.0-plugins-bad:amd64 1.24.2-1ubuntu4 +2025-11-21 01:59:15 status unpacked gstreamer1.0-plugins-bad:amd64 1.24.2-1ubuntu4 +2025-11-21 01:59:15 status half-configured gstreamer1.0-plugins-bad:amd64 1.24.2-1ubuntu4 +2025-11-21 01:59:15 status installed gstreamer1.0-plugins-bad:amd64 1.24.2-1ubuntu4 +2025-11-21 02:00:08 trigproc ca-certificates-java:all 20240118 +2025-11-21 02:00:08 status half-configured ca-certificates-java:all 20240118 +2025-11-21 02:00:08 status installed ca-certificates-java:all 20240118 +``` + +**What I Learned:** +- Shows package installation history +- Tracks configuration states (unpacked, half-configured, installed) +- Timestamps help correlate issues with package changes +- Useful for troubleshooting "what changed?" + +--- + +## 🔧 Mini Troubleshooting Exercise + +### Scenario: Check System Health + +**Step 1: Check if system is under load** +```bash +uptime +# Result: load average: 0.00, 0.00, 0.00 - System idle ✓ +``` + +**Step 2: Check memory availability** +```bash +free -h +# Result: 9.0Gi available - Plenty of memory ✓ +``` + +**Step 3: Check disk space** +```bash +df -h +# Result: / is 1% used - No disk space issues ✓ +``` + +**Step 4: Check for zombie processes** +```bash +ps aux | grep -i zombie +# Result: No zombie processes found ✓ +``` + +**Step 5: Review recent system messages** +```bash +dmesg | tail -10 +# Result: System boot completed successfully ✓ +``` + +**Conclusion:** System is healthy with no resource constraints or process issues. + +--- + +## 🎯 Key Takeaways + +### Process Commands Mastered: +1. `ps aux` - Detailed process snapshot +2. `pgrep -a` - Find processes by name +3. `top -b -n 1` - Resource monitoring snapshot +4. `ps -ef` - Process hierarchy view + +### System Monitoring: +1. `df -h` - Disk usage +2. `free -h` - Memory usage +3. `uptime` - Load and uptime + +### Log Analysis: +1. `dmesg` - Kernel messages +2. `tail -n 20 ` - Recent log entries +3. `ls -lah /var/log/` - Available logs + +--- + +## 💡 Pro Tips Learned + +1. **Always use `-h` flag** for human-readable output (df -h, free -h) +2. **Pipe to head/tail** to limit output: `ps aux | head -20` +3. **Use pgrep instead of ps | grep** - faster and cleaner +4. **Check logs in /var/log/** when troubleshooting +5. **Load average** should be below number of CPU cores +6. **Container environments** may not have systemd (use alternative commands) + +--- + +## 📚 Commands Summary + +| Category | Command | Purpose | +|----------|---------|---------| +| Process | `ps aux` | List all processes | +| Process | `pgrep -a ` | Find process by name | +| Process | `ps -ef` | Process hierarchy | +| Monitor | `top -b -n 1` | System snapshot | +| Monitor | `uptime` | Load average | +| Disk | `df -h` | Disk usage | +| Memory | `free -h` | Memory usage | +| Logs | `dmesg` | Kernel messages | +| Logs | `tail -n 20 ` | Recent log entries | +| Logs | `ls -lah /var/log/` | List log files | + +--- + +## 🔄 Next Steps + +1. Practice these commands on a full Linux system with systemd +2. Explore `journalctl` for systemd service logs +3. Learn to use `htop` (interactive process viewer) +4. Study log file locations for different services +5. Practice troubleshooting workflows + +--- + +**Practice Environment:** Container-based Ubuntu 24 +**Note:** Some commands (systemctl) not available in container - alternative approaches used +**Created for:** #90DaysOfDevOps #DevOpsKaJosh #TrainWithShubham + +# Beginner's Guide to Linux Services & Logs +**Simple, Hands-On Guide for Managing Services** + +--- + +## 🎯 What You'll Learn + +By the end of this guide, you'll know how to: +1. Check if a service is running +2. Start, stop, and restart services +3. Read service logs +4. Troubleshoot basic service issues + +**No prior experience needed!** Just follow along step-by-step. + +--- + +## 📚 Part 1: Understanding Services + +### What is a Service? + +A **service** is a program that runs in the background on your Linux system. + +**Common examples:** +- `ssh` - Allows remote login to your server +- `nginx` - Web server that serves websites +- `mysql` - Database server +- `cron` - Runs scheduled tasks +- `docker` - Container platform + +Think of services like apps on your phone that run in the background. + +--- + +## 🔧 Part 2: Basic Service Commands (systemctl) + +### Command 1: Check Service Status + +**The most important command you'll use daily:** + +```bash +systemctl status +``` + +**Example: Check SSH service** + +```bash +systemctl status ssh +``` + +**What you'll see:** + +``` +● ssh.service - OpenBSD Secure Shell server + Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled) + Active: active (running) since Wed 2026-02-08 10:00:00 UTC; 2h ago + Main PID: 1234 (sshd) + Tasks: 1 (limit: 4915) + Memory: 2.5M +``` + +**How to read this:** + +| Line | What it means | +|------|---------------| +| `Loaded: loaded` | Service configuration found ✓ | +| `Active: active (running)` | Service is running ✓ | +| `enabled` | Will start automatically on boot ✓ | +| `Main PID: 1234` | Process ID of the service | +| `Tasks: 1` | Number of running tasks | + +**Quick status check:** +- 🟢 Green dot `●` + `active (running)` = Service is running fine +- 🔴 Red dot `●` + `failed` = Service has a problem +- ⚪ White dot `●` + `inactive (dead)` = Service is stopped + +--- + +### Command 2: List All Services + +**See all services on your system:** + +```bash +systemctl list-units --type=service +``` + +**Too many results? Filter for running services only:** + +```bash +systemctl list-units --type=service --state=running +``` + +**Example output:** + +``` +UNIT LOAD ACTIVE SUB DESCRIPTION +ssh.service loaded active running OpenBSD Secure Shell server +cron.service loaded active running Regular background program +nginx.service loaded active running A high performance web server +``` + +**What each column means:** +- `UNIT` - Service name +- `LOAD` - Configuration loaded? +- `ACTIVE` - Is it running? +- `SUB` - Detailed state +- `DESCRIPTION` - What the service does + +--- + +### Command 3: Start a Service + +**Start a stopped service:** + +```bash +sudo systemctl start +``` + +**Example:** + +```bash +sudo systemctl start nginx +``` + +**Note:** You need `sudo` (admin rights) to manage services. + +--- + +### Command 4: Stop a Service + +**Stop a running service:** + +```bash +sudo systemctl stop +``` + +**Example:** + +```bash +sudo systemctl stop nginx +``` + +--- + +### Command 5: Restart a Service + +**Restart a service (stop + start):** + +```bash +sudo systemctl restart +``` + +**When to use:** +- After changing configuration files +- When service is misbehaving +- After updates + +**Example:** + +```bash +sudo systemctl restart nginx +``` + +--- + +### Command 6: Reload Configuration + +**Reload config without stopping service:** + +```bash +sudo systemctl reload +``` + +**Difference between reload and restart:** +- `reload` - Service keeps running, just re-reads config (no downtime) +- `restart` - Service stops and starts (brief downtime) + +--- + +### Command 7: Enable Service at Boot + +**Make service start automatically when system boots:** + +```bash +sudo systemctl enable +``` + +**Example:** + +```bash +sudo systemctl enable nginx +``` + +--- + +### Command 8: Disable Service at Boot + +**Prevent service from starting automatically:** + +```bash +sudo systemctl disable +``` + +--- + +### Command 9: Check Failed Services + +**Find services that have problems:** + +```bash +systemctl --failed +``` + +**Example output:** + +``` +UNIT LOAD ACTIVE SUB DESCRIPTION +myapp.service loaded failed failed My Application Service +``` + +--- + +## 📝 Part 3: Reading Service Logs + +### Why Check Logs? + +Logs tell you: +- What the service is doing +- If there are errors +- Why a service failed + +--- + +### Command 10: View Service Logs (journalctl) + +**Basic syntax:** + +```bash +journalctl -u +``` + +**Example: View SSH logs** + +```bash +journalctl -u ssh +``` + +**Output example:** + +``` +Feb 08 10:15:23 server sshd[1234]: Accepted password for user from 192.168.1.100 +Feb 08 10:20:45 server sshd[1234]: pam_unix(sshd:session): session opened +Feb 08 10:25:30 server sshd[5678]: Failed password for invalid user admin +``` + +**Tip:** Use arrow keys to scroll, press `q` to quit. + +--- + +### Command 11: View Last N Lines of Logs + +**See only recent logs:** + +```bash +journalctl -u -n 50 +``` + +**Example: Last 20 SSH log entries** + +```bash +journalctl -u ssh -n 20 +``` + +**Why use this?** +- Faster than viewing all logs +- Good for quick checks + +--- + +### Command 12: Follow Logs in Real-Time + +**Watch logs as they happen (like tail -f):** + +```bash +journalctl -u -f +``` + +**Example: Watch nginx logs live** + +```bash +journalctl -u nginx -f +``` + +**You'll see new entries appear in real-time:** + +``` +Feb 08 10:30:45 server nginx[5678]: 192.168.1.100 - "GET / HTTP/1.1" 200 +Feb 08 10:30:50 server nginx[5678]: 192.168.1.101 - "GET /about HTTP/1.1" 200 +``` + +**Press Ctrl+C to stop following.** + +--- + +### Command 13: View Logs from Last Hour + +**Filter by time:** + +```bash +journalctl -u --since "1 hour ago" +``` + +**More time examples:** + +```bash +# Last 30 minutes +journalctl -u nginx --since "30 minutes ago" + +# Since today +journalctl -u ssh --since today + +# Since specific time +journalctl -u nginx --since "2026-02-08 10:00:00" +``` + +--- + +### Command 14: View Only Errors + +**Filter by priority (errors only):** + +```bash +journalctl -u -p err +``` + +**Example:** + +```bash +journalctl -u nginx -p err +``` + +**Priority levels (from worst to least severe):** +- `emerg` - Emergency (0) +- `alert` - Alert (1) +- `crit` - Critical (2) +- `err` - Error (3) +- `warning` - Warning (4) +- `notice` - Notice (5) +- `info` - Info (6) +- `debug` - Debug (7) + +**Common usage:** + +```bash +# Show errors and warnings +journalctl -u myapp -p warning +``` + +--- + +### Command 15: Traditional Log Files (tail) + +**Some logs still in text files at /var/log/** + +```bash +tail -n 50 /var/log/syslog +``` + +**Follow a log file:** + +```bash +tail -f /var/log/nginx/error.log +``` + +**View specific log file:** + +```bash +# System log +tail -n 50 /var/log/syslog + +# Nginx access log +tail -n 100 /var/log/nginx/access.log + +# Nginx error log +tail -n 50 /var/log/nginx/error.log + +# Apache logs +tail -n 50 /var/log/apache2/error.log +``` + +--- + +## 🎓 Part 4: Hands-On Example - Inspecting SSH Service + +Let's inspect the **SSH service** step-by-step. + +### Step 1: Check if SSH is Running + +```bash +systemctl status ssh +``` + +**Look for:** +- Green dot and "active (running)" = Good! ✓ +- Red dot and "failed" = Problem! ✗ + +--- + +### Step 2: View Recent SSH Logs + +```bash +journalctl -u ssh -n 50 +``` + +**What to look for:** +- `Accepted password` - Successful login +- `Failed password` - Failed login attempt +- `Connection closed` - User disconnected + +--- + +### Step 3: Check for Failed Login Attempts + +```bash +journalctl -u ssh | grep "Failed" +``` + +**Example output:** + +``` +Feb 08 09:15:23 server sshd[1234]: Failed password for invalid user admin from 192.168.1.200 +Feb 08 09:20:45 server sshd[5678]: Failed password for root from 192.168.1.201 +``` + +**This shows someone tried to login and failed!** + +--- + +### Step 4: Watch Live SSH Activity + +```bash +journalctl -u ssh -f +``` + +**Now try to SSH to your server from another terminal.** +**You'll see the login attempt appear in real-time!** + +--- + +### Step 5: Check SSH Errors Only + +```bash +journalctl -u ssh -p err --since today +``` + +**If empty = No errors today! ✓** + +--- + +### Step 6: Restart SSH (if needed) + +```bash +sudo systemctl restart ssh +``` + +**Then check status again:** + +```bash +systemctl status ssh +``` + +--- + +## 🔥 Part 5: Common Troubleshooting Workflows + +### Problem: Service Won't Start + +**Follow these steps:** + +```bash +# Step 1: Try to start it +sudo systemctl start nginx + +# Step 2: Check status +systemctl status nginx + +# Step 3: Check logs for errors +journalctl -u nginx -n 50 + +# Step 4: Look for specific error messages +journalctl -u nginx -p err + +# Step 5: Fix the issue (config file, permissions, etc.) + +# Step 6: Restart +sudo systemctl restart nginx +``` + +--- + +### Problem: Service Keeps Failing + +```bash +# Step 1: Check what's wrong +systemctl status myapp + +# Step 2: View detailed logs +journalctl -u myapp -n 100 + +# Step 3: Check recent errors +journalctl -u myapp -p err --since "10 minutes ago" + +# Step 4: Watch while restarting +journalctl -u myapp -f +# (in another terminal: sudo systemctl restart myapp) +``` + +--- + +### Problem: Web Server Not Responding + +```bash +# Step 1: Is it running? +systemctl status nginx + +# Step 2: Check error logs +journalctl -u nginx -p err + +# Or traditional log file: +tail -n 50 /var/log/nginx/error.log + +# Step 3: Check access logs +tail -n 50 /var/log/nginx/access.log + +# Step 4: Restart if needed +sudo systemctl restart nginx +``` + +--- + +## 📋 Quick Reference Card + +### Service Management + +| Task | Command | +|------|---------| +| Check status | `systemctl status ` | +| Start service | `sudo systemctl start ` | +| Stop service | `sudo systemctl stop ` | +| Restart service | `sudo systemctl restart ` | +| Enable at boot | `sudo systemctl enable ` | +| Disable at boot | `sudo systemctl disable ` | +| List running | `systemctl list-units --type=service --state=running` | +| Find failed | `systemctl --failed` | + +### Log Viewing + +| Task | Command | +|------|---------| +| View logs | `journalctl -u ` | +| Last 50 lines | `journalctl -u -n 50` | +| Follow live | `journalctl -u -f` | +| Since 1 hour | `journalctl -u --since "1 hour ago"` | +| Errors only | `journalctl -u -p err` | +| Today's logs | `journalctl -u --since today` | +| Text log file | `tail -n 50 /var/log/` | +| Follow text log | `tail -f /var/log/` | + +--- + +## 💡 Pro Tips for Beginners + +### 1. Always Check Status First + +Before doing anything, check if service is running: + +```bash +systemctl status +``` + +--- + +### 2. Use -n to Limit Output + +Don't overwhelm yourself with millions of log lines: + +```bash +journalctl -u nginx -n 20 # Just last 20 lines +``` + +--- + +### 3. Grep is Your Friend + +Search for specific words: + +```bash +journalctl -u ssh | grep "Failed" +journalctl -u nginx | grep "error" +``` + +--- + +### 4. Restart is Safe + +When in doubt, restart: + +```bash +sudo systemctl restart +``` + +It's like "turn it off and on again" - often fixes issues! + +--- + +### 5. Check Logs After Restart + +Always verify restart worked: + +```bash +sudo systemctl restart nginx +systemctl status nginx +journalctl -u nginx -n 20 +``` + +--- + +## 🎯 Practice Exercise + +**Try this with SSH service:** + +1. Check SSH status +2. View last 20 SSH logs +3. Follow SSH logs in real-time (open new terminal and SSH to server) +4. Check for any failed login attempts today +5. Restart SSH service +6. Verify it restarted successfully + +**Commands:** + +```bash +# 1. Status +systemctl status ssh + +# 2. Last 20 logs +journalctl -u ssh -n 20 + +# 3. Follow logs +journalctl -u ssh -f + +# 4. Failed logins +journalctl -u ssh --since today | grep "Failed" + +# 5. Restart +sudo systemctl restart ssh + +# 6. Verify +systemctl status ssh +``` + +--- + +## 🚀 Next Steps + +Once comfortable with these basics: + +1. Learn about **log rotation** (keeping logs from filling disk) +2. Explore **systemd timers** (like cron jobs) +3. Study **service dependencies** (services that need other services) +4. Practice **creating custom services** + +--- + +## ❓ Common Questions + +### Q: What if journalctl says "No entries"? + +**A:** Either: +- Service hasn't logged anything yet +- You misspelled the service name +- Service isn't installed + +**Check:** `systemctl list-units --type=service | grep ` + +--- + +### Q: Do I always need sudo? + +**A:** +- ✅ Viewing logs/status: **No sudo needed** +- ⛔ Starting/stopping services: **Sudo required** + +```bash +# No sudo needed +systemctl status nginx +journalctl -u nginx + +# Sudo needed +sudo systemctl restart nginx +sudo systemctl enable nginx +``` + +--- + +### Q: How do I know what services are important? + +**A:** Start with these: + +- `ssh` - Remote access (important!) +- `nginx` or `apache2` - Web server +- `mysql` or `postgresql` - Database +- `docker` - If using containers +- `cron` - Scheduled tasks + +--- + +### Q: What's the difference between systemctl and service? + +**A:** +- `systemctl` - **Modern** (systemd) +- `service` - **Old** (legacy) + +**Use systemctl** on modern Linux systems (Ubuntu 16.04+, CentOS 7+, etc.) + +--- + +## 📝 Summary + +**You now know how to:** + +✅ Check if a service is running (`systemctl status`) +✅ Start, stop, restart services (`systemctl start/stop/restart`) +✅ View service logs (`journalctl -u `) +✅ Follow logs in real-time (`journalctl -u -f`) +✅ Find errors in logs (`journalctl -p err`) +✅ Troubleshoot basic service issues + +**Practice makes perfect!** Try these commands on your own system. + +--- + +**Created for:** #90DaysOfDevOps #DevOpsKaJosh #TrainWithShubham +**Remember:** When in doubt, check the status and logs! 🚀 \ No newline at end of file diff --git a/2026/day-06/file-io-practice.md b/2026/day-06/file-io-practice.md new file mode 100644 index 0000000000..5f704ff251 --- /dev/null +++ b/2026/day-06/file-io-practice.md @@ -0,0 +1,595 @@ +# Day 06 - File I/O Practice Log +**Linux File Read and Write Operations** + +Date: February 08, 2026 +Practice File: `notes.txt` + +--- + +## 🎯 Learning Objectives + +Today I practiced: +- Creating files with `touch` +- Writing to files using redirection (`>` and `>>`) +- Reading files with `cat`, `head`, and `tail` +- Using `tee` to write and display simultaneously + +--- + +## 📝 Step-by-Step Practice + +### Step 1: Create Empty File + +**Command:** +```bash +touch notes.txt +``` + +**Verification:** +```bash +ls -lh notes.txt +``` + +**Output:** +``` +-rw-r--r-- 1 root root 0 Feb 8 07:33 notes.txt +``` + +**What I Learned:** +- `touch` creates an empty file if it doesn't exist +- File size is 0 bytes (empty) +- Default permissions are `-rw-r--r--` (readable by all, writable by owner only) + +--- + +### Step 2: Write First Line (Overwrite) + +**Command:** +```bash +echo "Day 06: Learning Linux file operations" > notes.txt +``` + +**Read the file:** +```bash +cat notes.txt +``` + +**Output:** +``` +Day 06: Learning Linux file operations +``` + +**What I Learned:** +- `>` redirects output to a file +- `>` **OVERWRITES** the file (deletes previous content) +- `echo` prints text to standard output +- Be careful with `>` - it destroys existing content! + +--- + +### Step 3: Append Second Line + +**Command:** +```bash +echo "This is my second line of text" >> notes.txt +``` + +**Read the file:** +```bash +cat notes.txt +``` + +**Output:** +``` +Day 06: Learning Linux file operations +This is my second line of text +``` + +**What I Learned:** +- `>>` **APPENDS** to a file (adds to the end) +- `>>` does NOT overwrite existing content +- Much safer than `>` when adding to existing files + +--- + +### Step 4: Append Third Line + +**Command:** +```bash +echo "Third line added using append operator" >> notes.txt +``` + +**Read the file:** +```bash +cat notes.txt +``` + +**Output:** +``` +Day 06: Learning Linux file operations +This is my second line of text +Third line added using append operator +``` + +**What I Learned:** +- Can use `>>` multiple times safely +- Each line is added on a new line automatically +- File grows with each append operation + +--- + +### Step 5: Using tee Command + +**Command:** +```bash +echo "Fourth line using tee command" | tee -a notes.txt +``` + +**Output (displayed on screen):** +``` +Fourth line using tee command +``` + +**Read the file:** +```bash +cat notes.txt +``` + +**File content:** +``` +Day 06: Learning Linux file operations +This is my second line of text +Third line added using append operator +Fourth line using tee command +``` + +**What I Learned:** +- `tee` writes to file AND displays on screen simultaneously +- `|` (pipe) sends output from `echo` to `tee` +- `-a` flag means append (like `>>`) +- Without `-a`, tee would overwrite (like `>`) +- Very useful for logging while seeing output + +--- + +### Step 6: Add More Content + +**Commands:** +```bash +echo "Commands practiced: touch, cat, echo, tee" >> notes.txt +echo "head, tail, and redirection operators" >> notes.txt +``` + +**Read full file:** +```bash +cat notes.txt +``` + +**Output:** +``` +Day 06: Learning Linux file operations +This is my second line of text +Third line added using append operator +Fourth line using tee command +Commands practiced: touch, cat, echo, tee +head, tail, and redirection operators +``` + +--- + +### Step 7: Read First 3 Lines (head) + +**Command:** +```bash +head -n 3 notes.txt +``` + +**Output:** +``` +Day 06: Learning Linux file operations +This is my second line of text +Third line added using append operator +``` + +**What I Learned:** +- `head` shows the beginning of a file +- `-n 3` means "show first 3 lines" +- Default is 10 lines if you don't specify +- Useful for checking file headers or previewing files + +--- + +### Step 8: Read Last 2 Lines (tail) + +**Command:** +```bash +tail -n 2 notes.txt +``` + +**Output:** +``` +Commands practiced: touch, cat, echo, tee +head, tail, and redirection operators +``` + +**What I Learned:** +- `tail` shows the end of a file +- `-n 2` means "show last 2 lines" +- Default is 10 lines if you don't specify +- Very useful for checking recent log entries +- Can use `tail -f` to follow file changes in real-time + +--- + +### Step 9: Count Lines in File + +**Command:** +```bash +wc -l notes.txt +``` + +**Output:** +``` +6 notes.txt +``` + +**What I Learned:** +- `wc` means "word count" +- `-l` flag counts lines +- File has 6 lines total +- Can also use `-w` for words, `-c` for characters + +--- + +### Step 10: Display with Line Numbers + +**Command:** +```bash +cat -n notes.txt +``` + +**Output:** +``` + 1 Day 06: Learning Linux file operations + 2 This is my second line of text + 3 Third line added using append operator + 4 Fourth line using tee command + 5 Commands practiced: touch, cat, echo, tee + 6 head, tail, and redirection operators +``` + +**What I Learned:** +- `cat -n` adds line numbers +- Very helpful for debugging scripts +- Makes it easy to reference specific lines +- Numbers are aligned for readability + +--- + +### Step 11: More tee Practice + +**Commands:** +```bash +echo "=== Additional Practice ===" | tee -a notes.txt +echo "File created on: $(date)" | tee -a notes.txt +``` + +**Output (displayed on screen):** +``` +=== Additional Practice === +File created on: Sun Feb 8 07:33:41 UTC 2026 +``` + +**What I Learned:** +- Can use `$(date)` to embed current date/time +- `tee` shows output immediately (good for logging) +- `tee` can write to multiple files at once: `tee file1.txt file2.txt` + +--- + +### Step 12: Final File Content + +**Command:** +```bash +cat notes.txt +``` + +**Complete Output:** +``` +Day 06: Learning Linux file operations +This is my second line of text +Third line added using append operator +Fourth line using tee command +Commands practiced: touch, cat, echo, tee +head, tail, and redirection operators +=== Additional Practice === +File created on: Sun Feb 8 07:33:41 UTC 2026 +``` + +**Total Lines:** 8 +**File Successfully Created!** ✓ + +--- + +## 📊 Commands Summary Table + +| Command | Purpose | Example | +|---------|---------|---------| +| `touch file.txt` | Create empty file | `touch notes.txt` | +| `echo "text" > file` | Write (overwrite) | `echo "Hello" > notes.txt` | +| `echo "text" >> file` | Append | `echo "World" >> notes.txt` | +| `cat file` | Read entire file | `cat notes.txt` | +| `cat -n file` | Read with line numbers | `cat -n notes.txt` | +| `head -n N file` | Read first N lines | `head -n 3 notes.txt` | +| `tail -n N file` | Read last N lines | `tail -n 2 notes.txt` | +| `echo "text" \| tee file` | Write and display | `echo "Hi" \| tee notes.txt` | +| `echo "text" \| tee -a file` | Append and display | `echo "Hi" \| tee -a notes.txt` | +| `wc -l file` | Count lines | `wc -l notes.txt` | + +--- + +## 🔑 Key Concepts Learned + +### Redirection Operators + +**Single `>` (Output Redirection - OVERWRITE)** +```bash +echo "New content" > file.txt +# DANGER: This DELETES everything in file.txt first! +``` + +**Double `>>` (Output Redirection - APPEND)** +```bash +echo "Additional content" >> file.txt +# SAFE: This ADDS to the end of file.txt +``` + +**Remember:** +- `>` = Replace everything (dangerous!) +- `>>` = Add to end (safe) + +--- + +### Pipe Operator `|` + +**What it does:** Sends output from one command to another + +```bash +echo "Hello" | tee file.txt +# ↑ ↑ ↑ +# command1 pipe command2 +``` + +**Command1 output becomes Command2 input** + +--- + +### Reading Commands + +| Command | Use Case | +|---------|----------| +| `cat` | Read entire file (small files) | +| `head` | Preview beginning (check headers) | +| `tail` | Check end (recent logs) | +| `tail -f` | Follow live updates (real-time logs) | + +--- + +## 💡 Pro Tips Discovered + +### 1. Always Use `>>` for Logs +```bash +# Good - adds to log +echo "[$(date)] Process started" >> app.log + +# Bad - destroys previous logs! +echo "[$(date)] Process started" > app.log +``` + +--- + +### 2. Preview Before Processing +```bash +# Check first few lines before processing entire file +head -n 5 large-file.txt + +# Check if file format is correct +head -n 1 data.csv +``` + +--- + +### 3. tee for Logging +```bash +# Save to log AND see output +./my-script.sh | tee -a script.log +``` + +--- + +### 4. Combine Commands +```bash +# Count how many error lines in a log +grep "ERROR" app.log | wc -l + +# Show last 20 errors +grep "ERROR" app.log | tail -n 20 +``` + +--- + +## 🎯 Real-World DevOps Use Cases + +### Use Case 1: Creating Config Files +```bash +# Create new config file +touch /etc/myapp/config.txt + +# Add configuration +echo "port=8080" >> /etc/myapp/config.txt +echo "host=localhost" >> /etc/myapp/config.txt +echo "debug=true" >> /etc/myapp/config.txt +``` + +--- + +### Use Case 2: Checking Log Files +```bash +# Check recent errors (last 50 lines) +tail -n 50 /var/log/nginx/error.log + +# Follow live logs +tail -f /var/log/application.log + +# Check log file beginning (configuration info often at top) +head -n 20 /var/log/app.log +``` + +--- + +### Use Case 3: Deployment Logging +```bash +# Log deployment with timestamp and visibility +echo "[$(date)] Starting deployment v2.1.0" | tee -a deploy.log +./deploy.sh | tee -a deploy.log +echo "[$(date)] Deployment completed" | tee -a deploy.log +``` + +--- + +### Use Case 4: Quick File Creation +```bash +# Create script file +cat > backup.sh << 'EOF' +#!/bin/bash +echo "Starting backup..." +tar -czf backup.tar.gz /data +echo "Backup complete" +EOF + +# Make it executable +chmod +x backup.sh +``` + +--- + +## ⚠️ Common Mistakes to Avoid + +### Mistake 1: Using `>` Instead of `>>` +```bash +# WRONG - destroys log file every time! +echo "Log entry" > app.log + +# RIGHT - adds to log file +echo "Log entry" >> app.log +``` + +--- + +### Mistake 2: Forgetting `-a` with tee +```bash +# WRONG - overwrites file +echo "New entry" | tee logfile.txt + +# RIGHT - appends to file +echo "New entry" | tee -a logfile.txt +``` + +--- + +### Mistake 3: Not Checking File First +```bash +# WRONG - might overwrite important data +echo "test" > data.txt + +# RIGHT - check if file exists +ls -l data.txt +cat data.txt # See what's there +echo "test" >> data.txt # Then append if safe +``` + +--- + +## 🔄 Practice Exercise + +**Challenge:** Create a system info file + +```bash +# Create file with system info +echo "=== System Information ===" > sysinfo.txt +echo "Date: $(date)" >> sysinfo.txt +echo "Hostname: $(hostname)" >> sysinfo.txt +echo "Current User: $(whoami)" >> sysinfo.txt +echo "Current Directory: $(pwd)" >> sysinfo.txt +echo "" >> sysinfo.txt +echo "Disk Usage:" >> sysinfo.txt +df -h >> sysinfo.txt + +# View the result +cat sysinfo.txt +``` + +--- + +## 📚 What's Next? + +Now that I understand basic file I/O, next steps: +1. Learn file permissions (`chmod`, `chown`) +2. Practice with larger files +3. Learn text processing (`grep`, `sed`, `awk`) +4. Explore file compression (`tar`, `gzip`) +5. Master log rotation concepts + +--- + +## 🎓 Summary + +### ✅ Skills Acquired Today: + +1. **File Creation** - `touch` command +2. **Writing** - `>` for overwrite, `>>` for append +3. **Reading** - `cat`, `head`, `tail` +4. **Dual Output** - `tee` command +5. **Piping** - `|` operator +6. **Line Counting** - `wc -l` +7. **Numbered Output** - `cat -n` + +### 🔥 Most Useful Commands: + +- `tail -f` - Follow log files in real-time +- `>>` - Safe append to files +- `tee -a` - Log and display simultaneously +- `head/tail -n` - Quick file preview + +### 💪 Key Takeaway: + +**File operations are the foundation of DevOps work.** Almost everything in Linux is a file - configs, logs, scripts. Mastering these basic commands makes debugging and automation much faster! + +--- + +**Practice File:** `notes.txt` (8 lines created successfully) +**Commands Practiced:** 12 different file operations +**Created for:** #90DaysOfDevOps #DevOpsKaJosh #TrainWithShubham + +--- + +## 📝 Personal Notes + +**What I found most useful:** +- `tee -a` for deployment logging +- `tail -f` will be essential for monitoring +- `>>` is much safer than `>` for production + +**What surprised me:** +- How powerful simple redirection operators are +- `cat -n` is great for debugging scripts +- `tee` can write to multiple files at once + +**What I'll practice more:** +- Combining commands with pipes +- Real-time log monitoring with `tail -f` +- Using these commands in automation scripts + +--- + +**Tomorrow:** Moving on to text processing and searching! 🚀 \ No newline at end of file diff --git a/2026/day-07/day-07-linux-fs-and-scenarios.md b/2026/day-07/day-07-linux-fs-and-scenarios.md new file mode 100644 index 0000000000..91d3494ed2 --- /dev/null +++ b/2026/day-07/day-07-linux-fs-and-scenarios.md @@ -0,0 +1,314 @@ +``` +2026/day-07/day-07-linux-fs-and-scenarios.md +``` + +--- + +# Day 07 — Linux File System Hierarchy & Scenario Practice + +## Part 1: Linux File System Hierarchy + +### Core Directories (Must Know) + +#### `/` (root) + +* The top-level directory; everything in Linux starts from here. +* Contains all other directories and system files. + +**Example contents (ls -l /):** + +* `bin`, `etc`, `home`, `var` + +**I would use this when:** Navigating the system or locating any directory from the absolute path. + +--- + +#### `/home` + +* Contains personal directories for regular users. +* Stores user files, downloads, configs, etc. + +**Example contents (ls -l /home):** + +* `user`, `ubuntu` + +**I would use this when:** Accessing or managing user data. + +--- + +#### `/root` + +* Home directory of the root (administrator) user. +* Separate from `/home` for security. + +**Example contents (ls -l /root):** + +* `.bashrc`, `.ssh` + +**I would use this when:** Performing administrative tasks as root. + +--- + +#### `/etc` + +* Stores system-wide configuration files. +* Critical for system behavior and service configs. + +**Example contents (ls -l /etc):** + +* `hostname`, `ssh/`, `passwd` + +**I would use this when:** Modifying system or service configurations. + +--- + +#### `/var/log` + +* Contains system and application log files. +* Essential for troubleshooting and monitoring. + +**Example contents (ls -l /var/log):** + +* `syslog`, `auth.log`, `kern.log` + +**I would use this when:** Diagnosing errors, failures, or unusual behavior. + +--- + +#### `/tmp` + +* Stores temporary files created by applications. +* Usually cleared on reboot. + +**Example contents (ls -l /tmp):** + +* Temporary folders and session files + +**I would use this when:** Applications need short-term storage. + +--- + +### Additional Directories (Good to Know) + +#### `/bin` + +* Contains essential command binaries required for boot and basic operation. + +**Example contents (ls -l /bin):** + +* `ls`, `cp`, `mv`, `cat` + +**I would use this when:** Running core commands even in minimal environments. + +--- + +#### `/usr/bin` + +* Contains most user-level command binaries. +* Larger collection than `/bin`. + +**Example contents (ls -l /usr/bin):** + +* `git`, `python`, `vim` + +**I would use this when:** Running installed applications and tools. + +--- + +#### `/opt` + +* Used for optional or third-party software installations. + +**Example contents (ls -l /opt):** + +* `google/`, `docker/`, custom apps + +**I would use this when:** Managing manually installed software packages. + +--- + +### Hands-on Tasks + +**Find largest log files:** + +```bash +du -sh /var/log/* 2>/dev/null | sort -h | tail -5 +``` + +--- + +**View hostname config:** + +```bash +cat /etc/hostname +``` + +--- + +**Check home directory contents:** + +```bash +ls -la ~ +``` + +--- + +## Part 2: Scenario-Based Practice + +### Scenario 1: Service Not Starting + +**Problem:** Service `myapp` failed after reboot. + +**Step 1:** Check service status + +```bash +systemctl status myapp +``` + +**Why:** Determines whether the service is active, failed, or inactive. + +--- + +**Step 2:** Check recent logs + +```bash +journalctl -u myapp -n 50 +``` + +**Why:** Shows error messages explaining why it failed. + +--- + +**Step 3:** Check if enabled on boot + +```bash +systemctl is-enabled myapp +``` + +**Why:** Confirms whether it should start automatically. + +--- + +**Step 4:** Try starting manually + +```bash +systemctl start myapp +``` + +**Why:** Tests if the service can start now and produces fresh logs. + +--- + +### Scenario 2: High CPU Usage + +**Problem:** Server is slow. + +**Step 1:** View live CPU usage + +```bash +top +``` + +**Why:** Shows real-time CPU consumption by processes. + +--- + +**Step 2:** Use enhanced viewer (if installed) + +```bash +htop +``` + +**Why:** Easier to read and sort processes interactively. + +--- + +**Step 3:** List top CPU-consuming processes + +```bash +ps aux --sort=-%cpu | head -10 +``` + +**Why:** Identifies the processes using the most CPU and their PIDs. + +--- + +### Scenario 3: Finding Docker Service Logs + +**Step 1:** Check service status + +```bash +systemctl status docker +``` + +**Why:** Confirms service state and shows recent logs. + +--- + +**Step 2:** View recent logs + +```bash +journalctl -u docker -n 50 +``` + +**Why:** Retrieves last 50 log entries from systemd journal. + +--- + +**Step 3:** Follow logs in real time + +```bash +journalctl -u docker -f +``` + +**Why:** Monitors live activity for troubleshooting ongoing issues. + +--- + +### Scenario 4: File Permissions Issue + +**Problem:** Script not executable (`Permission denied`) + +**Step 1:** Check permissions + +```bash +ls -l /home/user/backup.sh +``` + +Look for: `-rw-r--r--` (no execute permission) + +--- + +**Step 2:** Add execute permission + +```bash +chmod +x /home/user/backup.sh +``` + +--- + +**Step 3:** Verify change + +```bash +ls -l /home/user/backup.sh +``` + +Look for: `-rwxr-xr-x` + +--- + +**Step 4:** Run the script + +```bash +./backup.sh +``` + +--- + +## Key Takeaways + +* Linux file system hierarchy tells you where configs, logs, binaries, and user data live. +* Logs and service status checks are the first steps in most troubleshooting workflows. +* Understanding permissions is critical for executing scripts and securing systems. +* Scenario-based practice mirrors real DevOps incidents and interview questions. + diff --git a/2026/day-08/day-08-cloud-deployment.md b/2026/day-08/day-08-cloud-deployment.md new file mode 100644 index 0000000000..75ff45ecd3 --- /dev/null +++ b/2026/day-08/day-08-cloud-deployment.md @@ -0,0 +1,262 @@ +Below is a **production-grade, step-by-step execution guide** for Day 08. Follow it exactly and you will have a publicly accessible Nginx server running on a cloud VM, plus logs extracted and downloaded. + +--- + +# ✅ Day 08 — Cloud Server Setup: Docker, Nginx & Web Deployment + +## Part 1 — Launch Instance & SSH Access + +### 🔹 Step 1: Create Cloud VM (AWS EC2 — Recommended) + +**Configuration (Free Tier Safe):** + +* AMI: **Ubuntu Server 22.04 LTS** +* Instance type: `t2.micro` +* Key pair: Create new `.pem` +* Network: + + * Allow SSH (22) — your IP only + * Allow HTTP (80) — Anywhere (0.0.0.0/0) + +Launch instance → wait until **Running** + +Copy **Public IPv4 Address** + +--- + +### 🔹 Step 2: Connect via SSH + +#### On Linux / Mac / Windows (WSL or Git Bash) + +```bash +chmod 400 your-key.pem + +ssh -i your-key.pem ubuntu@ +``` + +#### On Windows (PuTTY) + +Convert `.pem` → `.ppk` using PuTTYgen, then connect. + +--- + +## Part 2 — Install Docker & Nginx + +> Note: The task says Docker + Nginx. We’ll install both, but run Nginx directly (simpler for beginners). + +### 🔹 Step 1: Update System + +```bash +sudo apt update && sudo apt upgrade -y +``` + +--- + +### 🔹 Step 2: Install Docker + +```bash +sudo apt install docker.io -y +sudo systemctl enable docker +sudo systemctl start docker +sudo systemctl status docker +``` + +Verify: + +```bash +docker --version +``` + +--- + +### 🔹 Step 3: Install Nginx + +```bash +sudo apt install nginx -y +``` + +Start + enable: + +```bash +sudo systemctl enable nginx +sudo systemctl start nginx +sudo systemctl status nginx +``` + +If running, you will see: + +``` +Active: active (running) +``` + +--- + +## Part 3 — Security Group Configuration + +Ensure inbound rules: + +| Type | Port | Source | +| ---- | ---- | --------- | +| HTTP | 80 | 0.0.0.0/0 | +| SSH | 22 | Your IP | + +--- + +### 🔹 Test Web Access + +Open browser: + +``` +http:// +``` + +You should see: + +## 🎉 “Welcome to Nginx!” page + +📸 Take screenshot: `nginx-webpage.png` + +--- + +## Part 4 — Extract Nginx Logs + +Nginx logs are stored in: + +``` +/var/log/nginx/ +``` + +--- + +### 🔹 Step 1: View Logs + +Access log (visits): + +```bash +sudo cat /var/log/nginx/access.log +``` + +Error log: + +```bash +sudo cat /var/log/nginx/error.log +``` + +--- + +### 🔹 Step 2: Save Logs to File + +Copy access log to home directory: + +```bash +sudo cp /var/log/nginx/access.log ~/nginx-logs.txt +``` + +Fix permissions: + +```bash +sudo chown ubuntu:ubuntu ~/nginx-logs.txt +``` + +Verify: + +```bash +cat nginx-logs.txt +``` + +📸 Screenshot log output + +--- + +### 🔹 Step 3: Download Log File to Local Machine + +Run from your LOCAL terminal: + +#### AWS: + +```bash +scp -i your-key.pem ubuntu@:~/nginx-logs.txt . +``` + +#### Utho: + +```bash +scp root@:~/nginx-logs.txt . +``` + +File will appear in your current folder. + +--- + +# 📄 Ready-to-Submit Markdown File + +Create: + +``` +day-08-cloud-deployment.md +``` + +Paste this template: + +```markdown +# Day 08 — Cloud Server Deployment + +## Commands Used + +### SSH Connection +ssh -i your-key.pem ubuntu@ + +### System Update +sudo apt update && sudo apt upgrade -y + +### Install Docker +sudo apt install docker.io -y +sudo systemctl enable docker +sudo systemctl start docker + +### Install Nginx +sudo apt install nginx -y +sudo systemctl enable nginx +sudo systemctl start nginx + +### View Logs +sudo cat /var/log/nginx/access.log + +### Save Logs +sudo cp /var/log/nginx/access.log ~/nginx-logs.txt + +### Download Logs +scp -i your-key.pem ubuntu@:~/nginx-logs.txt . + +--- + +## Challenges Faced + +- SSH permission denied due to incorrect key permissions +- HTTP access initially blocked because port 80 was not enabled +- Solved by updating security group rules + +--- + +## What I Learned + +- How to launch and connect to a cloud VM +- How to install and manage services on Linux +- Basics of Docker installation +- How Nginx serves web traffic +- How to access and export server logs +``` + +--- + +# 🎯 What You Just Practiced (Real DevOps Skills) + +This mirrors real production workflows: + +* Infrastructure provisioning (IaaS) +* Remote administration via SSH +* Service installation & management +* Firewall / security configuration +* Log extraction for debugging +* Public web deployment + diff --git a/2026/day-09/day-09-user-management.md b/2026/day-09/day-09-user-management.md new file mode 100644 index 0000000000..66e8b1fe16 --- /dev/null +++ b/2026/day-09/day-09-user-management.md @@ -0,0 +1,147 @@ +# Day 09 Challenge – Linux User & Group Management + +## Users & Groups Created + +- **Users:** tokyo, berlin, professor, nairobi +- **Groups:** developers, admins, project-team + +--- + +## Group Assignments + +| User | Groups | +|-----------|-------------------------------| +| tokyo | developers, project-team | +| berlin | developers, admins | +| professor | admins | +| nairobi | project-team | + +--- + +## Directories Created + +| Directory | Group Owner | Permissions | +|---------------------|--------------|-------------| +| `/opt/dev-project` | developers | 775 (rwxrwxr-x) | +| `/opt/team-workspace` | project-team | 775 (rwxrwxr-x) | + +--- + +## Commands Used + +### Task 1 – Create Users + +```bash +# Create users with home directories +sudo useradd -m tokyo +sudo useradd -m berlin +sudo useradd -m professor + +# Set passwords +sudo passwd tokyo +sudo passwd berlin +sudo passwd professor + +# Verify users in /etc/passwd +grep -E "tokyo|berlin|professor" /etc/passwd + +# Verify home directories +ls /home/ +``` + +### Task 2 – Create Groups + +```bash +# Create groups +sudo groupadd developers +sudo groupadd admins + +# Verify groups +grep -E "developers|admins" /etc/group +``` + +### Task 3 – Assign Users to Groups + +```bash +# tokyo → developers +sudo usermod -aG developers tokyo + +# berlin → developers + admins +sudo usermod -aG developers,admins berlin + +# professor → admins +sudo usermod -aG admins professor + +# Verify group memberships +groups tokyo +groups berlin +groups professor +``` + +### Task 4 – Shared Directory (dev-project) + +```bash +# Create directory +sudo mkdir -p /opt/dev-project + +# Set group owner +sudo chgrp developers /opt/dev-project + +# Set permissions +sudo chmod 775 /opt/dev-project + +# Verify +ls -ld /opt/dev-project + +# Test file creation as tokyo +sudo -u tokyo touch /opt/dev-project/tokyo-file.txt + +# Test file creation as berlin +sudo -u berlin touch /opt/dev-project/berlin-file.txt + +# Verify files +ls -l /opt/dev-project/ +``` + +### Task 5 – Team Workspace + +```bash +# Create user nairobi +sudo useradd -m nairobi +sudo passwd nairobi + +# Create group project-team +sudo groupadd project-team + +# Add nairobi and tokyo to project-team +sudo usermod -aG project-team nairobi +sudo usermod -aG project-team tokyo + +# Create workspace directory +sudo mkdir -p /opt/team-workspace + +# Set group and permissions +sudo chgrp project-team /opt/team-workspace +sudo chmod 775 /opt/team-workspace + +# Verify +ls -ld /opt/team-workspace +groups nairobi +groups tokyo + +# Test file creation as nairobi +sudo -u nairobi touch /opt/team-workspace/nairobi-file.txt + +# Verify +ls -l /opt/team-workspace/ +``` + +--- + +## What I Learned + +1. **`useradd -m` is essential** – the `-m` flag automatically creates the user's home directory. Without it, the user exists in `/etc/passwd` but has no home directory, which causes login issues. + +2. **`usermod -aG` must use both flags** – `-a` (append) combined with `-G` (groups) adds the user to a group *without removing them from existing groups*. Using `-G` alone overwrites all current group memberships, which is an easy mistake to make. + +3. **Group permissions enable real collaboration** – setting directory group ownership (`chgrp`) and using permission `775` lets every member of a group read, write, and execute in a shared directory, while keeping outsiders restricted to read-only access. This is the foundation of how shared project directories work in real DevOps environments (e.g., CI/CD pipelines, shared build directories). \ No newline at end of file diff --git a/2026/day-10/day-10-file-permissions.md b/2026/day-10/day-10-file-permissions.md new file mode 100644 index 0000000000..73bfa0c115 --- /dev/null +++ b/2026/day-10/day-10-file-permissions.md @@ -0,0 +1,350 @@ + +# ✅ Day 10 — File Permissions & File Operations Challenge + +## 🔹 Task 1 — Create Files + +### 1) Create empty file + +```bash +touch devops.txt +``` + +--- + +### 2) Create file with content (using echo) + +```bash +echo "These are my DevOps notes." > notes.txt +``` + +(Alternative) + +```bash +cat > notes.txt +# Type content → press Ctrl+D to save +``` + +--- + +### 3) Create script using vim + +```bash +vim script.sh +``` + +Press `i` → insert mode → add: + +```bash +echo "Hello DevOps" +``` + +Save: + +``` +Esc → :wq → Enter +``` + +--- + +### ✔ Verify + +```bash +ls -l +``` + +Typical output: + +``` +-rw-r--r-- devops.txt +-rw-r--r-- notes.txt +-rw-r--r-- script.sh +``` + +--- + +## 🔹 Task 2 — Read Files + +### 1) Read notes.txt + +```bash +cat notes.txt +``` + +--- + +### 2) View script in vim read-only mode + +```bash +vim -R script.sh +``` + +Quit: + +``` +:q +``` + +--- + +### 3) First 5 lines of /etc/passwd + +```bash +head -n 5 /etc/passwd +``` + +--- + +### 4) Last 5 lines + +```bash +tail -n 5 /etc/passwd +``` + +--- + +## 🔹 Task 3 — Understand Permissions + +Check: + +```bash +ls -l devops.txt notes.txt script.sh +``` + +Example: + +``` +-rw-r--r-- 1 user user 0 devops.txt +-rw-r--r-- 1 user user 24 notes.txt +-rw-r--r-- 1 user user 20 script.sh +``` + +### 🔎 Interpretation + +Permission format: + +``` +Owner | Group | Others +rw- r-- r-- +``` + +Meaning: + +| File | Owner | Group | Others | +| ---------- | ------------ | ----- | ------ | +| devops.txt | Read + Write | Read | Read | +| notes.txt | Read + Write | Read | Read | +| script.sh | Read + Write | Read | Read | + +➡️ No execute permission yet. + +--- + +## 🔹 Task 4 — Modify Permissions + +### 1) Make script executable + +```bash +chmod +x script.sh +``` + +Verify: + +```bash +ls -l script.sh +``` + +Run: + +```bash +./script.sh +``` + +Output: + +``` +Hello DevOps +``` + +--- + +### 2) Make devops.txt read-only + +Remove write permission for all: + +```bash +chmod a-w devops.txt +``` + +Verify: + +``` +-r--r--r-- devops.txt +``` + +--- + +### 3) Set notes.txt to 640 + +```bash +chmod 640 notes.txt +``` + +Meaning: + +* Owner → read + write +* Group → read only +* Others → none + +Verify: + +``` +-rw-r----- notes.txt +``` + +--- + +### 4) Create directory with 755 + +```bash +mkdir project +chmod 755 project +``` + +Verify: + +```bash +ls -ld project +``` + +Expected: + +``` +drwxr-xr-x project +``` + +--- + +## 🔹 Task 5 — Test Permissions + +### 1) Write to read-only file + +```bash +echo "New text" >> devops.txt +``` + +Result: + +``` +Permission denied +``` + +--- + +### 2) Execute file without execute permission + +Remove execute: + +```bash +chmod -x script.sh +``` + +Run: + +```bash +./script.sh +``` + +Result: + +``` +Permission denied +``` + +--- + +# 📄 Ready-to-Submit Markdown File + +Create: + +``` +day-10-file-permissions.md +``` + +Paste: + +```markdown +# Day 10 Challenge + +## Files Created + +- devops.txt +- notes.txt +- script.sh +- project/ directory + +--- + +## Permission Changes + +script.sh: +- Before: rw-r--r-- +- After: rwxr-xr-x (executable) + +devops.txt: +- Before: rw-r--r-- +- After: r--r--r-- (read-only) + +notes.txt: +- Set to 640 → rw-r----- + +project/: +- Set to 755 → rwxr-xr-x + +--- + +## Commands Used + +touch devops.txt +echo "text" > notes.txt +vim script.sh +cat notes.txt +vim -R script.sh +head -n 5 /etc/passwd +tail -n 5 /etc/passwd +chmod +x script.sh +chmod a-w devops.txt +chmod 640 notes.txt +mkdir project +chmod 755 project + +--- + +## What I Learned + +- Linux permission model for owner, group, others +- How execute permission affects script execution +- Numeric vs symbolic chmod usage +``` + +--- + +# 🎯 Real DevOps Concepts You Practiced + +These are foundational production skills: + +### 🔹 Secure Script Deployment + +Executable flags control what can run on servers. + +### 🔹 Least Privilege Principle + +Restrict write/execute access to reduce risk. + +### 🔹 File System Security + +Critical for logs, configs, secrets, binaries. + +### 🔹 Debugging Permission Issues + +Common cause of production failures. + diff --git a/2026/day-11/day-11-file-ownership.md b/2026/day-11/day-11-file-ownership.md new file mode 100644 index 0000000000..5c22ba8576 --- /dev/null +++ b/2026/day-11/day-11-file-ownership.md @@ -0,0 +1,178 @@ +# Day 11 Challenge – File Ownership (chown & chgrp) + +## Files & Directories Created + +| File / Directory | Purpose | +|-----------------------------------------|----------------------------------| +| `devops-file.txt` | Task 2 – chown practice | +| `team-notes.txt` | Task 3 – chgrp practice | +| `project-config.yaml` | Task 4 – combined owner & group | +| `app-logs/` | Task 4 – directory ownership | +| `heist-project/` | Task 5 – recursive ownership | +| `heist-project/vault/gold.txt` | Task 5 – recursive test file | +| `heist-project/plans/strategy.conf` | Task 5 – recursive test file | +| `bank-heist/access-codes.txt` | Task 6 – individual ownership | +| `bank-heist/blueprints.pdf` | Task 6 – individual ownership | +| `bank-heist/escape-plan.txt` | Task 6 – individual ownership | + +--- + +## Ownership Changes + +| File / Directory | Before | After | +|-------------------------------------|-------------------------|-----------------------------| +| `devops-file.txt` | currentuser:currentuser | tokyo:currentuser | +| `devops-file.txt` | tokyo:currentuser | berlin:currentuser | +| `team-notes.txt` | currentuser:currentuser | currentuser:heist-team | +| `project-config.yaml` | currentuser:currentuser | professor:heist-team | +| `app-logs/` | currentuser:currentuser | berlin:heist-team | +| `heist-project/` (all contents) | currentuser:currentuser | professor:planners | +| `bank-heist/access-codes.txt` | currentuser:currentuser | tokyo:vault-team | +| `bank-heist/blueprints.pdf` | currentuser:currentuser | berlin:tech-team | +| `bank-heist/escape-plan.txt` | currentuser:currentuser | nairobi:vault-team | + +--- + +## Commands Used + +### Task 1 – Understanding Ownership + +```bash +# View ownership of files in home directory +ls -l ~ + +# Output format: permissions links owner group size date filename +# Example: -rw-r--r-- 1 alice alice 512 Feb 11 10:00 notes.txt +``` + +**Owner vs Group:** +The *owner* is the individual user account responsible for the file (has user-level permissions). The *group* is a collection of users — any user who belongs to that group receives the group-level permissions defined on the file. This separation allows fine-grained access: the owner can have full read/write access, the group can have read-only, and everyone else can be locked out. + +--- + +### Task 2 – Basic chown Operations + +```bash +# Create file +touch devops-file.txt + +# Check current ownership +ls -l devops-file.txt + +# Change owner to tokyo +sudo chown tokyo devops-file.txt + +# Verify +ls -l devops-file.txt + +# Change owner to berlin +sudo chown berlin devops-file.txt + +# Verify +ls -l devops-file.txt +``` + +--- + +### Task 3 – Basic chgrp Operations + +```bash +# Create file +touch team-notes.txt + +# Check current group +ls -l team-notes.txt + +# Create group +sudo groupadd heist-team + +# Change file group +sudo chgrp heist-team team-notes.txt + +# Verify +ls -l team-notes.txt +``` + +--- + +### Task 4 – Combined Owner & Group Change + +```bash +# Create file +touch project-config.yaml + +# Change owner AND group in one command +sudo chown professor:heist-team project-config.yaml + +# Verify +ls -l project-config.yaml + +# Create directory +mkdir app-logs + +# Change directory ownership +sudo chown berlin:heist-team app-logs/ + +# Verify +ls -ld app-logs/ +``` + +--- + +### Task 5 – Recursive Ownership + +```bash +# Create directory structure +mkdir -p heist-project/vault +mkdir -p heist-project/plans +touch heist-project/vault/gold.txt +touch heist-project/plans/strategy.conf + +# Create group +sudo groupadd planners + +# Recursively change ownership of entire directory +sudo chown -R professor:planners heist-project/ + +# Verify all files and subdirectories changed +ls -lR heist-project/ +``` + +--- + +### Task 6 – Practice Challenge + +```bash +# Create users (if not already created) +sudo useradd -m tokyo +sudo useradd -m berlin +sudo useradd -m nairobi + +# Create groups +sudo groupadd vault-team +sudo groupadd tech-team + +# Create directory and files +mkdir bank-heist/ +touch bank-heist/access-codes.txt +touch bank-heist/blueprints.pdf +touch bank-heist/escape-plan.txt + +# Set individual ownership +sudo chown tokyo:vault-team bank-heist/access-codes.txt +sudo chown berlin:tech-team bank-heist/blueprints.pdf +sudo chown nairobi:vault-team bank-heist/escape-plan.txt + +# Verify all at once +ls -l bank-heist/ +``` + +--- + +## What I Learned + +1. **`chown owner:group` does the work of two commands in one** – instead of running `chown` and `chgrp` separately, you can change both the owner and group simultaneously with `chown owner:group filename`. You can even use `chown :group filename` to change *only* the group, making `chgrp` mostly optional. + +2. **`-R` (recursive) is powerful but irreversible — verify first** – `sudo chown -R owner:group directory/` cascades ownership changes through every file and subdirectory instantly. In production, always run `ls -lR` first to understand what will be affected, because there's no undo and incorrect ownership on app files can break running services. + +3. **File ownership is the foundation of Linux security** – permissions (`chmod`) only matter in the context of who the owner and group are. A file set to `640` (rw-r-----) behaves completely differently depending on whether the accessing user is the owner, a group member, or neither. Getting ownership right is what makes shared DevOps directories, application deployments, and CI/CD pipeline artifacts work securely without over-exposing files to all users. \ No newline at end of file diff --git a/2026/day-13/day-13-lvm.md b/2026/day-13/day-13-lvm.md new file mode 100644 index 0000000000..10b87fb38b --- /dev/null +++ b/2026/day-13/day-13-lvm.md @@ -0,0 +1,222 @@ +# Day 13 Challenge – Linux Volume Management (LVM) + +## What is LVM? + +LVM (Logical Volume Manager) adds an abstraction layer between physical disks and the filesystems mounted on them. Instead of partitioning a disk directly, you pool one or more disks into a **Volume Group**, then carve out **Logical Volumes** from that pool. The key benefit: you can resize, extend, and snapshot volumes without unmounting or repartitioning — something traditional disk partitions can't do. + +``` +Physical Disks → Physical Volumes (PV) → Volume Group (VG) → Logical Volumes (LV) → Filesystem +``` + +--- + +## Setup – Creating a Virtual Disk (No Spare Disk Required) + +```bash +# Switch to root +sudo -i + +# Create a 1GB virtual disk image +dd if=/dev/zero of=/tmp/disk1.img bs=1M count=1024 + +# Attach it as a loop device +losetup -fP /tmp/disk1.img + +# Confirm the device name (e.g., /dev/loop0) +losetup -a +``` + +--- + +## Commands Used + +### Task 1 – Check Current Storage + +```bash +# List all block devices and their mount points +lsblk + +# Show existing Physical Volumes +pvs + +# Show existing Volume Groups +vgs + +# Show existing Logical Volumes +lvs + +# Show mounted filesystem disk usage +df -h +``` + +**What to look for:** +- `lsblk` shows your loop device (e.g., `loop0`) confirming it's ready to use +- `pvs`, `vgs`, `lvs` will be empty if this is a fresh setup — that's expected +- `df -h` shows currently mounted filesystems and available space + +--- + +### Task 2 – Create Physical Volume + +```bash +# Initialize the loop device as an LVM Physical Volume +# Replace /dev/loop0 with your actual device from losetup -a +pvcreate /dev/loop0 + +# Verify the Physical Volume was created +pvs +``` + +**Expected `pvs` output:** +``` + PV VG Fmt Attr PSize PFree + /dev/loop0 lvm2 --- 1024.00m 1024.00m +``` + +The PV exists but isn't assigned to a Volume Group yet — `VG` column is empty. + +--- + +### Task 3 – Create Volume Group + +```bash +# Create a Volume Group named 'devops-vg' from the Physical Volume +vgcreate devops-vg /dev/loop0 + +# Verify the Volume Group +vgs +``` + +**Expected `vgs` output:** +``` + VG #PV #LV #SN Attr VSize VFree + devops-vg 1 0 0 wz--n- 1020.00m 1020.00m +``` + +Notice `VSize` is slightly less than 1024MB — LVM reserves a small amount for metadata. + +--- + +### Task 4 – Create Logical Volume + +```bash +# Create a 500MB Logical Volume named 'app-data' inside devops-vg +lvcreate -L 500M -n app-data devops-vg + +# Verify the Logical Volume +lvs +``` + +**Expected `lvs` output:** +``` + LV VG Attr LSize Pool Origin Data% Meta% + app-data devops-vg -wi-a----- 500.00m +``` + +The LV now exists but has no filesystem yet — it's just a raw block device at `/dev/devops-vg/app-data`. + +--- + +### Task 5 – Format and Mount + +```bash +# Format the Logical Volume with ext4 filesystem +mkfs.ext4 /dev/devops-vg/app-data + +# Create a mount point +mkdir -p /mnt/app-data + +# Mount the Logical Volume +mount /dev/devops-vg/app-data /mnt/app-data + +# Verify it's mounted and check available space +df -h /mnt/app-data +``` + +**Expected `df -h` output:** +``` +Filesystem Size Used Avail Use% Mounted on +/dev/mapper/devops--vg-app--data 477M 28K 445M 1% /mnt/app-data +``` + +The volume is live and usable. Create a test file to confirm write access: + +```bash +touch /mnt/app-data/test-file.txt +ls -l /mnt/app-data/ +``` + +--- + +### Task 6 – Extend the Volume + +```bash +# Extend the Logical Volume by 200MB +lvextend -L +200M /dev/devops-vg/app-data + +# Resize the filesystem to use the newly added space +# (ext4 can do this live — no unmounting needed) +resize2fs /dev/devops-vg/app-data + +# Confirm the filesystem now reflects the larger size +df -h /mnt/app-data +``` + +**Expected `df -h` output after extension:** +``` +Filesystem Size Used Avail Use% Mounted on +/dev/mapper/devops--vg-app--data 673M 28K 625M 1% /mnt/app-data +``` + +The volume grew from ~477M to ~673M with zero downtime. The existing `test-file.txt` is untouched. + +--- + +## Full LVM Hierarchy – Final State + +```bash +# View the complete picture +pvs && vgs && lvs +``` + +``` + PV VG Fmt Attr PSize PFree + /dev/loop0 devops-vg lvm2 a-- 1020.00m 320.00m + + VG #PV #LV #SN Attr VSize VFree + devops-vg 1 1 0 wz--n- 1020.00m 320.00m + + LV VG Attr LSize Pool Origin Data% + app-data devops-vg -wi-ao---- 700.00m +``` + +--- + +## Cleanup (Optional) + +```bash +# Unmount +umount /mnt/app-data + +# Remove Logical Volume +lvremove /dev/devops-vg/app-data + +# Remove Volume Group +vgremove devops-vg + +# Remove Physical Volume +pvremove /dev/loop0 + +# Detach loop device +losetup -d /dev/loop0 +``` + +--- + +## What I Learned + +1. **LVM decouples storage from physical hardware** – Traditional disk partitions are fixed: once you set a size, shrinking or growing requires unmounting, repartitioning, and hoping the data survives. LVM's abstraction layer (PV → VG → LV) means you can extend a live, mounted volume in seconds with `lvextend` + `resize2fs`. In DevOps, this is critical for application servers and databases that can't afford downtime when disk usage spikes. + +2. **The loop device trick makes LVM learnable on any machine** – Using `dd` + `losetup` creates a fully functional virtual disk from a file, so you don't need a bare-metal server with spare drives to practice LVM. This same pattern is used in real environments: Docker storage drivers, VM disk images, and cloud instance boot volumes all use loop or similar virtual block devices under the hood. + +3. **`lvextend` and `resize2fs` are two separate steps for a reason** – `lvextend` grows the *block device* (the LVM layer), but the *filesystem* sitting on top of it doesn't automatically know about the extra space. You need `resize2fs` to tell ext4 to expand into the newly available blocks. For XFS filesystems the equivalent is `xfs_growfs`. Skipping `resize2fs` is a common mistake — the `df -h` output won't change and the space appears lost until you run it. \ No newline at end of file diff --git a/2026/day-14/day-14-networking.md b/2026/day-14/day-14-networking.md new file mode 100644 index 0000000000..33ee5d0412 --- /dev/null +++ b/2026/day-14/day-14-networking.md @@ -0,0 +1,227 @@ +# Day 14 Challenge – Networking Fundamentals & Hands-on Checks + +## Target Host for Today's Checks: `google.com` + +--- + +## Quick Concepts + +### OSI vs TCP/IP Models + +The **OSI model** is a 7-layer reference framework used to reason about where in the stack a problem lives. The **TCP/IP model** is the practical 4-layer implementation actually running on your machine. OSI is the map; TCP/IP is the road. + +| OSI Layer | Name | TCP/IP Layer | What lives here | +|-----------|--------------|--------------|----------------------------------------| +| L7 | Application | Application | HTTP, HTTPS, DNS, SSH, FTP | +| L6 | Presentation | Application | TLS/SSL encryption, encoding | +| L5 | Session | Application | Session management, sockets | +| L4 | Transport | Transport | TCP (reliable), UDP (fast/lossy) | +| L3 | Network | Internet | IP addressing, routing, ICMP | +| L2 | Data Link | Link | MAC addresses, Ethernet, Wi-Fi frames | +| L1 | Physical | Link | Cables, signals, hardware NICs | + +### Where Key Protocols Sit + +- **IP** → L3 Network / Internet layer — handles addressing and routing packets between machines +- **TCP/UDP** → L4 Transport layer — TCP guarantees delivery and order; UDP trades reliability for speed (DNS queries, video streams) +- **HTTP/HTTPS** → L7 Application layer — HTTPS is HTTP with TLS (L6) wrapping it before it hits TCP +- **DNS** → L7 Application layer, but carried over UDP (port 53) or TCP for large responses + +### Real Example + +``` +curl https://google.com +``` + +- **L7 Application:** curl constructs an HTTP GET request +- **L6 Presentation:** TLS handshake encrypts the request (HTTPS) +- **L4 Transport:** TCP (port 443) ensures packets arrive in order +- **L3 Network:** IP routes packets from your machine to Google's servers +- **L2/L1 Link/Physical:** Ethernet/Wi-Fi frames carry the IP packets over your NIC + +--- + +## Hands-on Checklist + +### Identity — `ip addr show` + +```bash +ip addr show +# or +hostname -I +``` + +``` +2: eth0: + inet 192.168.1.42/24 brd 192.168.1.255 scope global eth0 +``` + +**Observation:** Machine is on a private `192.168.1.0/24` subnet. The `/24` means 254 usable host addresses on this local network. Traffic to `google.com` will leave via the default gateway and get NAT'd to a public IP. + +--- + +### Reachability — `ping google.com` + +```bash +ping -c 5 google.com +``` + +``` +PING google.com (142.250.182.46) 56(84) bytes of data. +64 bytes from lga34s35-in-f14.1e100.net (142.250.182.46): icmp_seq=1 ttl=118 time=8.42 ms +64 bytes from lga34s35-in-f14.1e100.net (142.250.182.46): icmp_seq=2 ttl=118 time=7.98 ms +64 bytes from lga34s35-in-f14.1e100.net (142.250.182.46): icmp_seq=3 ttl=118 time=8.15 ms +64 bytes from lga34s35-in-f14.1e100.net (142.250.182.46): icmp_seq=4 ttl=118 time=8.23 ms +64 bytes from lga34s35-in-f14.1e100.net (142.250.182.46): icmp_seq=5 ttl=118 time=8.09 ms + +--- google.com ping statistics --- +5 packets transmitted, 5 received, 0% packet loss, time 4006ms +rtt min/avg/max/mdev = 7.98/8.17/8.42/0.15 ms +``` + +**Observation:** 0% packet loss, consistent ~8ms latency — clean L3 path to Google. The `ttl=118` means packets are passing through roughly 7 routers (TTL starts at 128 for Windows targets, 64 for Linux). If you see packet loss here, suspect a routing issue or firewall blocking ICMP before you blame the application. + +--- + +### Path — `traceroute google.com` + +```bash +traceroute google.com +``` + +``` +traceroute to google.com (142.250.182.46), 30 hops max, 60 byte packets + 1 _gateway (192.168.1.1) 0.452 ms 0.389 ms 0.401 ms + 2 10.0.0.1 (10.0.0.1) 1.823 ms 1.756 ms 1.799 ms + 3 isp-node1.provider.net 5.234 ms 5.198 ms 5.267 ms + 4 72.14.215.165 6.102 ms 6.087 ms 6.134 ms + 5 * * * + 6 lga34s35-in-f14.1e100.net 8.320 ms 8.289 ms 8.301 ms +``` + +**Observation:** 6 hops to Google. Hop 5 shows `* * *` — that router drops traceroute probes (ICMP TTL-exceeded), which is normal for many ISP and backbone routers. It's not a connectivity problem; the path continues and reaches the destination at hop 6. If you saw `* * *` from hop 5 onward with no final destination, *that's* when you'd investigate. + +--- + +### Ports — `ss -tulpn` + +```bash +ss -tulpn +``` + +``` +Netid State Recv-Q Send-Q Local Address:Port Peer Address:Port Process +udp UNCONN 0 0 127.0.0.53%lo:53 0.0.0.0:* users:(("systemd-resolve",pid=631)) +tcp LISTEN 0 128 0.0.0.0:22 0.0.0.0:* users:(("sshd",pid=843)) +tcp LISTEN 0 128 127.0.0.1:631 0.0.0.0:* users:(("cupsd",pid=712)) +tcp LISTEN 0 4096 127.0.0.53%lo:53 0.0.0.0:* users:(("systemd-resolve",pid=631)) +``` + +**Observation:** SSH (`sshd`) is listening on port 22 on all interfaces (`0.0.0.0:22`) — this machine accepts inbound SSH from anywhere the network allows. `systemd-resolved` listens on port 53 locally, acting as the DNS stub resolver. The `0.0.0.0` bind means exposed externally; `127.0.0.1` means loopback-only (internal). + +--- + +### Name Resolution — `dig google.com` + +```bash +dig google.com +``` + +``` +;; ANSWER SECTION: +google.com. 207 IN A 142.250.182.46 + +;; Query time: 3 msec +;; SERVER: 127.0.0.53#53(127.0.0.53) +;; MSG SIZE rcvd: 55 +``` + +**Observation:** `google.com` resolves to `142.250.182.46` in 3ms via the local stub resolver (`127.0.0.53`), which forwards to the upstream DNS server. The TTL of `207` seconds means this record will be cached locally for ~3.5 more minutes. A very high query time (200ms+) points to a slow upstream DNS server — switch to `8.8.8.8` or `1.1.1.1` in `/etc/resolv.conf` to test. + +--- + +### HTTP Check — `curl -I https://google.com` + +```bash +curl -I https://google.com +``` + +``` +HTTP/2 301 +content-type: text/html; charset=UTF-8 +location: https://www.google.com/ +server: gws +x-xss-protection: 0 +x-frame-options: SAMEORIGIN +``` + +**Observation:** Returns `301 Moved Permanently` — Google redirects `google.com` to `www.google.com`. This is expected behaviour, not an error. A `200 OK` would mean the content is served directly. If you saw `5xx` here, the issue is server-side; `4xx` means client-side (bad path, auth failure); connection refused means the service isn't running or a firewall is blocking port 443. + +--- + +### Connections Snapshot — `netstat -an | head -20` + +```bash +netstat -an | head -20 +``` + +``` +Active Internet connections (servers and established) +Proto Local Address Foreign Address State +tcp 0.0.0.0:22 0.0.0.0:* LISTEN +tcp 127.0.0.1:631 0.0.0.0:* LISTEN +tcp 192.168.1.42:22 192.168.1.10:54321 ESTABLISHED +tcp 192.168.1.42:54892 142.250.182.46:443 ESTABLISHED +``` + +**Observation:** 2 `LISTEN` entries (SSH, CUPS), 2 `ESTABLISHED` — one inbound SSH session from `192.168.1.10`, one outbound HTTPS connection to Google (from the `curl` command). A machine under load or attack often shows hundreds of `ESTABLISHED` or `TIME_WAIT` entries — `netstat -an | grep ESTABLISHED | wc -l` gives you the count fast. + +--- + +## Mini Task: Port Probe & Interpret + +**Identified port:** SSH on port `22` (from `ss -tulpn` above) + +```bash +nc -zv localhost 22 +``` + +``` +Connection to localhost (127.0.0.1) 22 port [tcp/ssh] succeeded! +``` + +**Result:** Port 22 is reachable. The `nc -zv` (zero I/O, verbose) probe confirmed the socket is open and accepting connections without needing SSH credentials. + +**If it had failed:** The next checks in order would be: +1. `systemctl status sshd` — is the service running? +2. `ss -tulpn | grep 22` — is it actually bound to that port? +3. `ufw status` or `iptables -L` — is a firewall dropping the connection? + +--- + +## Reflection + +### Which command gives you the fastest signal when something is broken? + +**`ping`** for raw reachability — one command tells you within seconds whether L3 connectivity exists and whether there's packet loss. If ping succeeds but the service is down, you've immediately isolated the problem to L4-L7. If ping fails, start at the network layer: routing, DNS, firewall. + +### What layer would you inspect next if DNS fails? + +DNS failure (e.g., `dig` returns `SERVFAIL` or times out) lives at **L7/Application**, but the fix is often at **L3** or the transport level. Check in this order: + +1. Can you reach the DNS server IP directly? `ping 8.8.8.8` — if this fails, you have an L3 routing problem, not a DNS problem. +2. Is port 53 open on the resolver? `nc -zv 8.8.8.8 53` — if blocked, a firewall (L3/L4) is the culprit. +3. Is `/etc/resolv.conf` pointing at the right nameserver? — configuration issue. + +### What layer if HTTP 500 shows up? + +`500 Internal Server Error` is a pure **L7 Application** issue — the network delivered the request correctly; the server-side application crashed or misconfigured. Next checks: + +1. `sudo journalctl -u nginx --since "5 minutes ago"` — read the web server error log +2. `systemctl status ` — check if the backend process is running +3. Check application logs in `/var/log//` for stack traces + +### Two follow-up checks in a real incident + +1. **`curl -v https://`** — verbose curl shows the full TLS handshake, HTTP headers, and response body, pinpointing exactly where a request breaks down (DNS → TCP connect → TLS → HTTP). +2. **`ss -tulpn` + `systemctl status `** — confirm the service is bound to the expected port and that the process is actually running. A surprising number of "networking issues" turn out to be a crashed service or a port conflict. \ No newline at end of file diff --git a/2026/day-15/day-15-networking-concepts.md b/2026/day-15/day-15-networking-concepts.md new file mode 100644 index 0000000000..68988d2a10 --- /dev/null +++ b/2026/day-15/day-15-networking-concepts.md @@ -0,0 +1,202 @@ +# Day 15 Challenge – DNS, IP Addressing, Subnets & Ports + +--- + +## Task 1: DNS – How Names Become IPs + +### What happens when you type `google.com` in a browser? + +1. Your browser checks its **local cache** first — if it resolved `google.com` recently and the TTL hasn't expired, it uses that IP immediately with no external query. +2. If not cached, the OS asks the **local resolver** (e.g., `127.0.0.53` via `systemd-resolved`), which checks its own cache and then forwards the query upstream. +3. The upstream resolver works through the DNS hierarchy: it asks a **Root nameserver** (`.`) which points to the **TLD nameserver** (`.com`), which points to **Google's authoritative nameserver** (`ns1.google.com`), which finally returns the actual IP address. +4. That IP travels back down the chain to your browser, which opens a TCP connection to it — the entire process typically takes under 5ms on a warm cache, 50–200ms on a cold lookup. + +### DNS Record Types + +| Record | Purpose | +|--------|---------| +| `A` | Maps a domain name to an **IPv4 address** — the most common record type; `google.com → 142.250.182.46` | +| `AAAA` | Maps a domain name to an **IPv6 address** — the 128-bit successor to A records; `google.com → 2607:f8b0:4004::200e` | +| `CNAME` | **Canonical Name** — an alias that points one domain to another domain (not an IP); `www.example.com → example.com` | +| `MX` | **Mail Exchange** — specifies which server handles email for a domain; priority-ordered so mail falls back gracefully | +| `NS` | **Name Server** — delegates authority for a domain to specific DNS servers; tells the world which servers are authoritative | + +### `dig google.com` Output + +```bash +dig google.com +``` + +``` +;; QUESTION SECTION: +;google.com. IN A + +;; ANSWER SECTION: +google.com. 207 IN A 142.250.182.46 + +;; Query time: 3 msec +;; SERVER: 127.0.0.53#53(127.0.0.53) +;; WHEN: Sat Feb 21 10:14:22 UTC 2026 +;; MSG SIZE rcvd: 55 +``` + +**A record:** `142.250.182.46` +**TTL:** `207` seconds — this record will be cached for ~3.5 more minutes. Once it expires, the next query triggers a full DNS lookup again. Short TTLs are used when an IP might change soon (e.g., during a migration); long TTLs reduce DNS query load. + +--- + +## Task 2: IP Addressing + +### What is an IPv4 address? + +An IPv4 address is a **32-bit number** written as four decimal octets separated by dots: `192.168.1.10`. Each octet represents 8 bits, so each ranges from 0–255. The total address space is 2³² = ~4.3 billion addresses — a number that seemed enormous in 1981 and is now exhausted, which is why IPv6 exists. + +The address has two logical parts: +- **Network portion** — identifies which network the host belongs to (determined by the subnet mask) +- **Host portion** — identifies the specific device within that network + +### Public vs Private IPs + +**Private IPs** are reserved for use inside local networks (LANs). They are not routable on the public internet — your router NATs them to a public IP for outbound traffic. + +**Public IPs** are globally unique and routable across the internet, assigned by ISPs and regional registries (ARIN, RIPE, etc.). + +| Type | Example | Who assigns it | +|---------|-------------------|------------------------| +| Private | `192.168.1.42` | Your router/DHCP server| +| Public | `142.250.182.46` | Your ISP / cloud provider | + +### Private IP Ranges (RFC 1918) + +| Range | CIDR | Typical use | +|-------------------------------|----------------|------------------------------------| +| `10.0.0.0 – 10.255.255.255` | `10.0.0.0/8` | Large enterprise networks, cloud VPCs | +| `172.16.0.0 – 172.31.255.255` | `172.16.0.0/12`| Docker default bridge networks | +| `192.168.0.0 – 192.168.255.255`| `192.168.0.0/16`| Home routers, small office LANs | + +### `ip addr show` – Identifying Private IPs + +```bash +ip addr show +``` + +``` +2: eth0: + inet 192.168.1.42/24 brd 192.168.1.255 scope global eth0 + inet6 fe80::a00:27ff:fe4b:c3d2/64 scope link +``` + +**`192.168.1.42`** falls in the `192.168.x.x` range — confirmed **private IP**. The `fe80::` IPv6 address is a link-local address, also non-routable. This machine has no public IP directly assigned; outbound internet traffic is NAT'd through the gateway at `192.168.1.1`. + +--- + +## Task 3: CIDR & Subnetting + +### What does `/24` mean in `192.168.1.0/24`? + +The `/24` is the **prefix length** — it means the first **24 bits** of the address are the network portion, and the remaining **8 bits** are for host addresses. Written as a subnet mask: `255.255.255.0`. In binary: + +``` +11111111.11111111.11111111.00000000 +``` + +The three `255` octets (all 1s) are fixed — they identify the network. The final `0` octet (all 0s) is the host range: `0–255`, giving 256 total addresses. + +### Usable Hosts Formula + +``` +Total IPs = 2^(32 - prefix) +Usable hosts = Total IPs - 2 +``` + +The 2 subtracted are the **network address** (all host bits = 0) and the **broadcast address** (all host bits = 1) — neither can be assigned to a device. + +### CIDR Reference Table + +| CIDR | Subnet Mask | Total IPs | Usable Hosts | +|------|-----------------|------------|--------------| +| /24 | 255.255.255.0 | 256 | 254 | +| /16 | 255.255.0.0 | 65,536 | 65,534 | +| /28 | 255.255.255.240 | 16 | 14 | + +**`/28` breakdown:** Used for small subnets — e.g., a dedicated subnet for 10 servers, a NAT gateway subnet, or a firewall DMZ. Only 14 usable addresses, so you won't accidentally expose more address space than needed. + +### Why Do We Subnet? + +Three real reasons: + +1. **Efficiency** — Giving a team of 10 servers a `/24` (254 addresses) wastes 244 IPs. A `/28` (14 hosts) fits perfectly. In cloud environments (AWS VPCs, GCP VPCs), wasted address space can block future expansion. +2. **Security isolation** — Traffic between subnets must pass through a router or firewall, where rules can be enforced. Putting databases in a private subnet (`10.0.2.0/24`) and web servers in a public subnet (`10.0.1.0/24`) means database traffic never hits the public internet by default. +3. **Broadcast containment** — Every device in a subnet receives broadcast traffic. A single flat `/16` with 65,534 hosts generates enormous broadcast noise. Splitting into smaller `/24` subnets keeps broadcast domains manageable. + +--- + +## Task 4: Ports – The Doors to Services + +### What is a port and why do we need them? + +An IP address gets a packet to the right **machine**. A port gets it to the right **process** on that machine. Ports are 16-bit numbers (0–65535) that the OS uses to multiplex network traffic — SSH, HTTP, and a database can all run on the same server because they bind to different ports. Without ports, the OS wouldn't know whether an incoming packet belongs to your web server or your SSH daemon. + +- **Well-known ports (0–1023):** Reserved for standard services; binding to these requires root/admin privileges +- **Registered ports (1024–49151):** Used by applications (databases, message queues, etc.) +- **Ephemeral ports (49152–65535):** Temporarily assigned by the OS to *outbound* connections (the "source port" on your end when you `curl` a website) + +### Common Ports Reference + +| Port | Service | Protocol | Notes | +|-------|-------------------|----------|-------------------------------------------------| +| 22 | SSH | TCP | Secure remote shell; always restrict by IP in production | +| 80 | HTTP | TCP | Unencrypted web traffic; typically redirects to 443 | +| 443 | HTTPS | TCP | TLS-encrypted web traffic; default for all modern web apps | +| 53 | DNS | UDP/TCP | UDP for standard queries; TCP for large responses/zone transfers | +| 3306 | MySQL / MariaDB | TCP | Default relational database port; should never be public-facing | +| 6379 | Redis | TCP | In-memory cache/message broker; binds to localhost by default | +| 27017 | MongoDB | TCP | Default NoSQL database port; authentication required in production | + +### `ss -tulpn` – Matching Ports to Services + +```bash +ss -tulpn +``` + +``` +Netid State Local Address:Port Process +udp UNCONN 127.0.0.53%lo:53 users:(("systemd-resolve",pid=631)) +tcp LISTEN 0.0.0.0:22 users:(("sshd",pid=843)) +tcp LISTEN 127.0.0.1:631 users:(("cupsd",pid=712)) +tcp LISTEN 127.0.0.53%lo:53 users:(("systemd-resolve",pid=631)) +``` + +**Match 1 — Port 22 → SSH (`sshd`):** Listening on `0.0.0.0:22` means it accepts connections on all network interfaces. In production, lock this down with firewall rules (`ufw allow from 10.0.0.0/8 to any port 22`) so only trusted subnets can reach it. + +**Match 2 — Port 53 → DNS (`systemd-resolved`):** The stub resolver listens on the loopback interface only (`127.0.0.53`) — it's not exposed externally, just serving DNS for processes on this machine and forwarding queries upstream. + +--- + +## Task 5: Putting It Together + +### `curl http://myapp.com:8080` — what's involved? + +1. **DNS resolution:** `myapp.com` is resolved to an IP via the DNS lookup chain (Task 1) — your resolver checks cache, queries upstream if needed, returns an A record. +2. **IP routing:** Your OS determines if `myapp.com`'s IP is on the local subnet or needs to route via the default gateway (Task 2 — public vs private). +3. **Port 8080:** A non-standard HTTP port (applications often use 8080 to avoid needing root for port 80). The OS opens an ephemeral source port on your end and connects to port 8080 on the remote host (Task 4). +4. **TCP + HTTP:** A TCP connection is established (SYN/SYN-ACK/ACK handshake), then an HTTP GET request is sent over it. No TLS since it's `http://`, not `https://`. + +### App can't reach database at `10.0.1.50:3306` — first checks? + +`10.0.1.50` is a private IP (Task 2), so this is internal traffic — likely between two servers in the same VPC or LAN. + +Check in this order: +1. **Is the database reachable at all?** `ping 10.0.1.50` — if this fails, it's a routing/firewall issue at L3, not a database problem. +2. **Is port 3306 open on the database server?** `nc -zv 10.0.1.50 3306` — a refused connection means MySQL isn't running or is bound to a different interface; a timeout means a firewall (security group, `iptables`, `ufw`) is blocking port 3306 between the two hosts. +3. **On the database server:** `ss -tulpn | grep 3306` — confirm MySQL is actually listening, and check whether it's bound to `127.0.0.1:3306` (loopback only, unreachable remotely) vs `0.0.0.0:3306` (all interfaces, reachable). + +--- + +## What I Learned + +1. **DNS is a distributed cache, not a single lookup** — the TTL on every record controls how long it lives in caches at every layer (browser, OS, resolver). When you change a DNS record, the old IP can persist for hours across the internet until TTLs expire everywhere. This is why DNS changes during migrations require lowering the TTL *days in advance* — it's not instant. + +2. **Subnetting is a security boundary, not just an addressing tool** — choosing the right CIDR isn't about conserving IPs (though that matters in cloud billing). It's about ensuring that traffic between tiers (web → app → database) has to cross a controlled boundary where firewall rules apply. A flat network where everything shares a `/16` is operationally simple but a security nightmare. + +3. **Ports tell you what's exposed; binding address tells you *to whom*** — a service listening on `0.0.0.0:3306` is reachable from any network interface (dangerous for a database). The same service on `127.0.0.1:3306` is loopback-only (safe for local connections only). Reading `ss -tulpn` output — specifically the `Local Address` column — is one of the fastest ways to audit what a server is actually exposing to the network. \ No newline at end of file diff --git a/2026/day-16/day-16-shell-scripting.md b/2026/day-16/day-16-shell-scripting.md new file mode 100644 index 0000000000..63fec63ddc --- /dev/null +++ b/2026/day-16/day-16-shell-scripting.md @@ -0,0 +1,220 @@ +# Day 16 Challenge – Shell Scripting Basics + +All scripts should be made executable before running: +```bash +chmod +x .sh +./.sh +``` + +--- + +## Task 1: Your First Script — `hello.sh` + +```bash +#!/bin/bash +echo "Hello, DevOps!" +``` + +**Output:** +``` +Hello, DevOps! +``` + +**What happens if you remove the shebang line?** + +Without `#!/bin/bash`, the kernel doesn't know which interpreter to use. If you run the script directly with `./hello.sh`, your current shell (usually bash or sh) is used as a fallback — so for simple scripts it may still work. However, this is unreliable: if `echo` behaviour or syntax differs between `sh` and `bash` (e.g., arrays, `[[ ]]` conditionals, process substitution), the script silently breaks or errors. The shebang is a guarantee — it pins the interpreter regardless of who runs the script or which shell they're using. + +--- + +## Task 2: Variables — `variables.sh` + +```bash +#!/bin/bash + +NAME="Alex" +ROLE="DevOps Engineer" + +# Double quotes expand variables +echo "Hello, I am $NAME and I am a $ROLE" + +# Single quotes treat everything literally +echo 'With single quotes: Hello, I am $NAME and I am a $ROLE' +``` + +**Output:** +``` +Hello, I am Alex and I am a DevOps Engineer +With single quotes: Hello, I am $NAME and I am a $ROLE +``` + +**Single quotes vs double quotes:** + +| Quote type | Behaviour | Use when | +|------------|-----------|----------| +| `"double"` | Variables and command substitutions (`$VAR`, `$(cmd)`) are expanded | You want variables to be interpreted | +| `'single'` | Everything is treated as a literal string — no expansion at all | You want the exact characters, e.g. printing a dollar sign or a regex pattern | + +**Key rule:** Never put spaces around `=` when assigning variables. `NAME = "Alex"` causes a syntax error — bash interprets `NAME` as a command, not an assignment. + +--- + +## Task 3: User Input — `greet.sh` + +```bash +#!/bin/bash + +read -p "Enter your name: " NAME +read -p "Enter your favourite tool: " TOOL + +echo "Hello $NAME, your favourite tool is $TOOL" +``` + +**Example run:** +``` +Enter your name: Alex +Enter your favourite tool: Terraform +Hello Alex, your favourite tool is Terraform +``` + +**`read` flags worth knowing:** +- `-p "prompt"` — displays a prompt on the same line before waiting for input +- `-s` — silent mode (hides input, useful for passwords) +- `-t 10` — times out after 10 seconds if no input is given + +--- + +## Task 4: If-Else Conditions + +### `check_number.sh` + +```bash +#!/bin/bash + +read -p "Enter a number: " NUM + +if [ "$NUM" -gt 0 ]; then + echo "$NUM is positive." +elif [ "$NUM" -lt 0 ]; then + echo "$NUM is negative." +else + echo "The number is zero." +fi +``` + +**Example runs:** +``` +Enter a number: 42 +42 is positive. + +Enter a number: -7 +-7 is negative. + +Enter a number: 0 +The number is zero. +``` + +**Integer comparison operators in bash:** + +| Operator | Meaning | +|----------|---------| +| `-eq` | equal to | +| `-ne` | not equal to | +| `-gt` | greater than | +| `-lt` | less than | +| `-ge` | greater than or equal | +| `-le` | less than or equal | + +--- + +### `file_check.sh` + +```bash +#!/bin/bash + +read -p "Enter a filename to check: " FILENAME + +if [ -f "$FILENAME" ]; then + echo "File '$FILENAME' exists." +else + echo "File '$FILENAME' does not exist." +fi +``` + +**Example runs:** +``` +Enter a filename to check: /etc/passwd +File '/etc/passwd' exists. + +Enter a filename to check: /tmp/nope.txt +File '/tmp/nope.txt' does not exist. +``` + +**Common file test operators:** + +| Flag | Tests for | +|------|-----------| +| `-f` | Regular file exists | +| `-d` | Directory exists | +| `-e` | File or directory exists (either) | +| `-r` | File is readable | +| `-w` | File is writable | +| `-x` | File is executable | +| `-s` | File exists and is non-empty | + +Always **quote the variable** (`"$FILENAME"`) — if the filename contains spaces, an unquoted variable breaks the test operator into multiple arguments. + +--- + +## Task 5: Combine It All — `server_check.sh` + +```bash +#!/bin/bash + +SERVICE="sshd" + +read -p "Do you want to check the status of '$SERVICE'? (y/n): " ANSWER + +if [ "$ANSWER" = "y" ]; then + STATUS=$(systemctl is-active "$SERVICE") + + if [ "$STATUS" = "active" ]; then + echo "$SERVICE is active and running." + else + echo "$SERVICE is NOT active. Current state: $STATUS" + fi +elif [ "$ANSWER" = "n" ]; then + echo "Skipped." +else + echo "Invalid input. Please enter 'y' or 'n'." +fi +``` + +**Example run (service active):** +``` +Do you want to check the status of 'sshd'? (y/n): y +sshd is active and running. +``` + +**Example run (service inactive):** +``` +Do you want to check the status of 'sshd'? (y/n): y +sshd is NOT active. Current state: inactive +``` + +**Example run (skip):** +``` +Do you want to check the status of 'sshd'? (y/n): n +Skipped. +``` + +**Key pattern — command substitution:** `STATUS=$(systemctl is-active "$SERVICE")` captures the output of a command into a variable. The `$(...)` syntax is the modern form; the older backtick form `` `command` `` works identically but is harder to nest and read. + +--- + +## What I Learned + +1. **The shebang line is a contract, not a courtesy** — `#!/bin/bash` doesn't just label the file; it's an instruction to the kernel to invoke that exact interpreter. Scripts without it are at the mercy of whatever shell the user happens to be running, which makes behaviour unpredictable across environments. In CI/CD pipelines where scripts run as non-interactive shells, missing shebangs are a common source of mysterious failures. + +2. **Quote your variables — always** — `[ $FILENAME ]` and `[ "$FILENAME" ]` look similar but behave very differently when the variable is empty or contains spaces. An unquoted empty variable causes `[ -f ]` with no argument, which is a syntax error; an unquoted variable with spaces gets word-split into multiple arguments. The rule is simple: double-quote every variable expansion unless you deliberately need word splitting. + +3. **`$()` command substitution is what makes scripts dynamic** — capturing command output into a variable (`STATUS=$(systemctl is-active sshd)`) is the bridge between running commands and making decisions based on their results. This pattern — run a command, store its output, branch on the value — is the core loop of almost every real-world ops script: check a service, check disk usage, check an API response, then act accordingly. \ No newline at end of file diff --git a/2026/day-17/day-17-scripting.md b/2026/day-17/day-17-scripting.md new file mode 100644 index 0000000000..de3bcd1f15 --- /dev/null +++ b/2026/day-17/day-17-scripting.md @@ -0,0 +1,345 @@ +# Day 17 Challenge – Shell Scripting: Loops, Arguments & Error Handling + +All scripts should be made executable before running: +```bash +chmod +x .sh +./.sh +``` + +--- + +## Task 1: For Loops + +### `for_loop.sh` — Iterating a list + +```bash +#!/bin/bash + +for fruit in apple banana cherry mango strawberry; do + echo "Fruit: $fruit" +done +``` + +**Output:** +``` +Fruit: apple +Fruit: banana +Fruit: cherry +Fruit: mango +Fruit: strawberry +``` + +--- + +### `count.sh` — Counting 1 to 10 + +```bash +#!/bin/bash + +for (( i=1; i<=10; i++ )); do + echo "$i" +done +``` + +**Output:** +``` +1 +2 +3 +4 +5 +6 +7 +8 +9 +10 +``` + +**Two for loop styles in bash:** + +| Style | Syntax | Best for | +|-------|--------|----------| +| List iteration | `for item in a b c; do` | Looping over words, filenames, array elements | +| C-style counter | `for (( i=1; i<=10; i++ ))` | Numeric ranges, index-based loops | + +You can also use `for i in {1..10}; do` as a shorter alternative to the C-style form for simple numeric ranges. + +--- + +## Task 2: While Loop + +### `countdown.sh` + +```bash +#!/bin/bash + +read -p "Enter a number to count down from: " NUM + +if ! [[ "$NUM" =~ ^[0-9]+$ ]]; then + echo "Error: Please enter a positive integer." + exit 1 +fi + +while [ "$NUM" -ge 0 ]; do + echo "$NUM" + (( NUM-- )) +done + +echo "Done!" +``` + +**Example run:** +``` +Enter a number to count down from: 5 +5 +4 +3 +2 +1 +0 +Done! +``` + +**Example run (bad input):** +``` +Enter a number to count down from: abc +Error: Please enter a positive integer. +``` + +**Key pattern — input validation with regex:** `[[ "$NUM" =~ ^[0-9]+$ ]]` checks that the input is only digits. The `!` negates it — if the input is *not* a number, we exit early. Always validate user input before using it in arithmetic — passing a string to `-ge` causes a cryptic error. + +**While loop anatomy:** +```bash +while [ condition ]; do + # body +done +``` +The condition is re-evaluated before every iteration. Use `break` to exit early; use `continue` to skip to the next iteration. + +--- + +## Task 3: Command-Line Arguments + +### `greet_args.sh` — Argument with usage guard + +```bash +#!/bin/bash + +if [ "$#" -eq 0 ]; then + echo "Usage: ./greet_args.sh " + exit 1 +fi + +NAME="$1" +echo "Hello, $NAME!" +``` + +**Example runs:** +``` +$ ./greet_args.sh Alex +Hello, Alex! + +$ ./greet_args.sh +Usage: ./greet_args.sh +``` + +--- + +### `args_demo.sh` — Inspecting all arguments + +```bash +#!/bin/bash + +echo "Script name : $0" +echo "Total args : $#" +echo "All args : $@" + +INDEX=1 +for arg in "$@"; do + echo " Arg $INDEX: $arg" + (( INDEX++ )) +done +``` + +**Example run:** +``` +$ ./args_demo.sh devops linux bash scripting +Script name : ./args_demo.sh +Total args : 4 +All args : devops linux bash scripting + Arg 1: devops + Arg 2: linux + Arg 3: bash + Arg 4: scripting +``` + +**Positional variable reference:** + +| Variable | Meaning | +|----------|---------| +| `$0` | The script's name (as invoked) | +| `$1` … `$9` | First through ninth argument | +| `${10}` | Tenth argument and beyond (braces required) | +| `$#` | Total number of arguments passed | +| `$@` | All arguments as separate quoted words — safe to loop over | +| `$*` | All arguments as a single string — loses argument boundaries if quoted differently | + +**Always prefer `"$@"` over `"$*"` when looping** — `"$@"` preserves argument boundaries even when arguments contain spaces (e.g., `"hello world"` stays as one argument, not two). + +--- + +## Task 4: Install Packages via Script + +### `install_packages.sh` + +```bash +#!/bin/bash + +# Root check +if [ "$EUID" -ne 0 ]; then + echo "Error: This script must be run as root. Use: sudo ./install_packages.sh" + exit 1 +fi + +PACKAGES=("nginx" "curl" "wget") + +echo "=== Package Installation Check ===" +echo "" + +for pkg in "${PACKAGES[@]}"; do + if dpkg -s "$pkg" &> /dev/null; then + echo "[SKIP] $pkg is already installed." + else + echo "[INSTALL] $pkg not found — installing..." + apt-get install -y "$pkg" &> /dev/null + + if dpkg -s "$pkg" &> /dev/null; then + echo "[OK] $pkg installed successfully." + else + echo "[ERROR] $pkg installation failed." + fi + fi +done + +echo "" +echo "=== Done ===" +``` + +**Example output (all already installed):** +``` +=== Package Installation Check === + +[SKIP] nginx is already installed. +[SKIP] curl is already installed. +[SKIP] wget is already installed. + +=== Done === +``` + +**Example output (nginx missing):** +``` +=== Package Installation Check === + +[INSTALL] nginx not found — installing... +[OK] nginx installed successfully. +[SKIP] curl is already installed. +[SKIP] wget is already installed. + +=== Done === +``` + +**Example output (run without root):** +``` +Error: This script must be run as root. Use: sudo ./install_packages.sh +``` + +**Key patterns:** + +- `PACKAGES=("nginx" "curl" "wget")` — bash array syntax; elements in parentheses, space-separated +- `"${PACKAGES[@]}"` — expand all array elements as separate quoted words (mirrors `"$@"` for arguments) +- `&> /dev/null` — redirects both stdout and stderr to `/dev/null`, suppressing all output from `dpkg -s` and `apt-get` so only our custom status messages are shown +- `$EUID` — the effective user ID; `0` means root. More reliable than checking `$USER = "root"` since `EUID` reflects `sudo` escalation correctly + +--- + +## Task 5: Error Handling + +### `safe_script.sh` + +```bash +#!/bin/bash + +set -e + +TARGET_DIR="/tmp/devops-test" +TARGET_FILE="$TARGET_DIR/hello.txt" + +echo "=== Safe Script: Error Handling Demo ===" +echo "" + +mkdir "$TARGET_DIR" || echo "[WARN] Directory '$TARGET_DIR' already exists — continuing." + +echo "[INFO] Changing into $TARGET_DIR" +cd "$TARGET_DIR" || { echo "[ERROR] Could not cd into $TARGET_DIR. Aborting."; exit 1; } + +echo "[INFO] Creating hello.txt" +touch hello.txt || { echo "[ERROR] Could not create hello.txt. Aborting."; exit 1; } + +echo "Hello from safe_script.sh — $(date)" > hello.txt + +echo "" +echo "[OK] All steps completed successfully." +echo "[OK] File contents:" +cat hello.txt +``` + +**First run (directory doesn't exist):** +``` +=== Safe Script: Error Handling Demo === + +[INFO] Changing into /tmp/devops-test +[INFO] Creating hello.txt + +[OK] All steps completed successfully. +[OK] File contents: +Hello from safe_script.sh — Sun Feb 22 10:30:00 UTC 2026 +``` + +**Second run (directory already exists):** +``` +=== Safe Script: Error Handling Demo === + +[WARN] Directory '/tmp/devops-test' already exists — continuing. +[INFO] Changing into /tmp/devops-test +[INFO] Creating hello.txt + +[OK] All steps completed successfully. +[OK] File contents: +Hello from safe_script.sh — Sun Feb 22 10:31:45 UTC 2026 +``` + +**Error handling patterns explained:** + +| Pattern | Behaviour | +|---------|-----------| +| `set -e` | Script exits immediately if any command returns a non-zero exit code — no silent failures | +| `cmd \|\| echo "message"` | If `cmd` fails, run the fallback (print message, use alternative command, etc.) | +| `cmd \|\| { echo "msg"; exit 1; }` | If `cmd` fails, print message *and* exit — the `{ }` groups multiple commands after `\|\|` | +| `set -u` | Exit if an undefined variable is used — catches typos like `$PACAKGES` | +| `set -o pipefail` | Makes a pipeline fail if *any* command in it fails, not just the last one | + +**Production-grade scripts typically open with:** +```bash +set -euo pipefail +``` +This catches exit code failures (`-e`), undefined variables (`-u`), and pipeline failures (`-o pipefail`) — the three most common sources of silent bugs in shell scripts. + +--- + +## What I Learned + +1. **`"$@"` vs `"$*"` is not a style choice — it's a correctness issue** — both expand all positional arguments, but `"$@"` keeps each argument as its own quoted word. If an argument contains a space (e.g., `"hello world"`), `"$@"` passes it as one argument, while `"$*"` splits it into two. In a loop like `for arg in "$@"`, this matters every time a user passes a filename with spaces. Defaulting to `"$@"` is the correct and safe habit. + +2. **`set -e` is a safety net, not a replacement for explicit error handling** — `set -e` silently exits the script the moment any command fails, which is better than a script that powers through errors and corrupts state. But combined with `||` fallbacks, you get the best of both worlds: the script halts on unexpected failures, while anticipated failures (like a directory already existing) are handled gracefully with a message instead of an abort. Use `set -euo pipefail` at the top of every non-trivial script. + +3. **Arrays make package lists maintainable** — hardcoding packages as a space-separated string (`PACKAGES="nginx curl wget"`) works until a package name contains a space or you need to do per-element operations. Bash arrays (`PACKAGES=("nginx" "curl" "wget")`) store elements cleanly and expand safely with `"${PACKAGES[@]}"`. In a real DevOps context — provisioning scripts, bootstrap automation, CI setup — the package list will change over time, and an array makes adding/removing entries a one-line edit with no risk of breaking the loop logic. \ No newline at end of file diff --git a/2026/day-18/day-18-scripting.md b/2026/day-18/day-18-scripting.md new file mode 100644 index 0000000000..3688518a7d --- /dev/null +++ b/2026/day-18/day-18-scripting.md @@ -0,0 +1,415 @@ +# Day 18 – Shell Scripting: Functions & Intermediate Concepts + +> **Goal:** Write cleaner, reusable scripts using functions, strict mode, local variables, and real-world patterns. + +--- + +## Task 1: Basic Functions — `functions.sh` + +### Script + +```bash +#!/bin/bash +# Task 1: Basic Functions + +greet() { + local name="$1" + echo "Hello, ${name}!" +} + +add() { + local a="$1" + local b="$2" + local sum=$(( a + b )) + echo "Sum of ${a} + ${b} = ${sum}" +} + +# Call both functions +greet "DevOps Engineer" +greet "Shubham" +add 10 25 +add 100 200 +``` + +### Output + +``` +Hello, DevOps Engineer! +Hello, Shubham! +Sum of 10 + 25 = 35 +Sum of 100 + 200 = 300 +``` + +### Explanation + +- Functions are defined with the syntax `function_name() { ... }` +- Arguments are accessed inside the function as `$1`, `$2`, etc. +- Using `local` for variables inside functions prevents them from leaking into global scope. + +--- + +## Task 2: Functions with Return Values — `disk_check.sh` + +### Script + +```bash +#!/bin/bash +# Task 2: Functions with Return Values + +check_disk() { + echo "=== Disk Usage ===" + df -h / + echo "" +} + +check_memory() { + echo "=== Memory Usage ===" + free -h + echo "" +} + +# Main section +check_disk +check_memory +``` + +### Output + +``` +=== Disk Usage === +Filesystem Size Used Avail Use% Mounted on +none 9.9G 2.2M 9.9G 1% / + +=== Memory Usage === + total used free shared buff/cache available +Mem: 9.0Gi 13Mi 9.0Gi 0B 9.7Mi 9.0Gi +Swap: 0B 0B 0B +``` + +### Explanation + +- Shell functions don't "return" values like other languages — they print output to stdout, which can be captured with `$(function_name)`. +- `df -h` shows human-readable disk usage; `free -h` shows human-readable memory stats. +- Each function acts as a self-contained unit — making the script modular and easy to maintain. + +--- + +## Task 3: Strict Mode — `strict_demo.sh` + +### What does each flag do? + +| Flag | Behavior | +|------|----------| +| `set -e` | **Exit immediately** if any command returns a non-zero exit code. Prevents the script from continuing after an error. | +| `set -u` | **Treat unset/undefined variables as errors.** Instead of silently using an empty string, the script exits immediately — catches typos in variable names. | +| `set -o pipefail` | **A pipeline fails if ANY command in it fails**, not just the last one. Without this, `false \| true` would exit 0. | + +### Script + +```bash +#!/bin/bash +# Task 3: Strict Mode Demo +set -euo pipefail + +echo "=== Strict Mode Demo ===" +echo "Script is running with set -euo pipefail" +echo "" + +# Demonstrating set -u: using undefined variable would cause immediate exit +# Uncomment below to see set -u in action: +# echo "Undefined: $UNDEFINED_VAR" + +# Demonstrating set -e: a failing command exits the script +# Uncomment below to see set -e in action: +# ls /nonexistent_directory + +# Demonstrating set -o pipefail: piped command failure +# Uncomment below to see pipefail in action: +# cat /nonexistent_file | grep "something" + +# Safe usage with defined variables +GREETING="Hello from strict mode!" +echo "$GREETING" + +if df -h / > /dev/null 2>&1; then + echo "Disk check passed." +fi + +echo "" +echo "Script completed successfully — strict mode kept things safe!" +``` + +### Output + +``` +=== Strict Mode Demo === +Script is running with set -euo pipefail + +Hello from strict mode! +Disk check passed. + +Script completed successfully — strict mode kept things safe! +``` + +### What happens when you violate each rule? + +**`set -u` — Undefined variable:** +```bash +echo "$UNDEFINED_VAR" +# → bash: UNDEFINED_VAR: unbound variable +# Script exits immediately with code 1 +``` + +**`set -e` — Failing command:** +```bash +ls /nonexistent_directory +# → ls: cannot access '/nonexistent_directory': No such file or directory +# Script exits immediately — no further commands run +``` + +**`set -o pipefail` — Failed pipe:** +```bash +cat /nonexistent_file | grep "something" +# → Without pipefail: exit code = 0 (grep succeeded, even though cat failed) +# → With pipefail: exit code = 1 (cat failed, so the whole pipeline fails) +``` + +--- + +## Task 4: Local Variables — `local_demo.sh` + +### Script + +```bash +#!/bin/bash +# Task 4: Local Variables Demo + +# Function using LOCAL variables (safe — no leakage) +with_local() { + local my_var="I am LOCAL" + local counter=42 + echo "[inside with_local] my_var = $my_var" + echo "[inside with_local] counter = $counter" +} + +# Function using GLOBAL variables (unsafe — leaks outside) +without_local() { + my_var="I am GLOBAL (leaked!)" + counter=99 + echo "[inside without_local] my_var = $my_var" + echo "[inside without_local] counter = $counter" +} + +echo "=== Test 1: Function with local variables ===" +with_local +echo "[outside] my_var = '${my_var:-NOT SET}'" +echo "[outside] counter = '${counter:-NOT SET}'" + +echo "" +echo "=== Test 2: Function without local variables ===" +without_local +echo "[outside] my_var = '${my_var:-NOT SET}'" +echo "[outside] counter = '${counter:-NOT SET}'" + +echo "" +echo "=== Key Takeaway ===" +echo "Always use 'local' inside functions to avoid polluting global scope!" +``` + +### Output + +``` +=== Test 1: Function with local variables === +[inside with_local] my_var = I am LOCAL +[inside with_local] counter = 42 +[outside] my_var = 'NOT SET' +[outside] counter = 'NOT SET' + +=== Test 2: Function without local variables === +[inside without_local] my_var = I am GLOBAL (leaked!) +[inside without_local] counter = 99 +[outside] my_var = 'I am GLOBAL (leaked!)' +[outside] counter = '99' + +=== Key Takeaway === +Always use 'local' inside functions to avoid polluting global scope! +``` + +### Explanation + +- When `local` is used, the variable only exists within the function's scope. +- Without `local`, variables set inside a function bleed into the global scope — this can cause subtle, hard-to-debug bugs when multiple functions use the same variable name. +- Always default to `local` in functions unless you specifically intend global side effects. + +--- + +## Task 5: System Info Reporter — `system_info.sh` + +### Script + +```bash +#!/bin/bash +# Task 5: System Info Reporter +set -euo pipefail + +SEPARATOR="==============================================" + +print_header() { + local title="$1" + echo "" + echo "$SEPARATOR" + echo " $title" + echo "$SEPARATOR" +} + +host_info() { + print_header "Hostname & OS Info" + echo "Hostname : $(hostname)" + echo "OS : $(uname -o 2>/dev/null || uname -s)" + echo "Kernel : $(uname -r)" + echo "Arch : $(uname -m)" + if [ -f /etc/os-release ]; then + local pretty_name + pretty_name=$(grep PRETTY_NAME /etc/os-release | cut -d= -f2 | tr -d '"') + echo "Distro : $pretty_name" + fi +} + +uptime_info() { + print_header "Uptime" + uptime -p 2>/dev/null || uptime + echo "Boot time : $(who -b 2>/dev/null | awk '{print $3, $4}' || echo 'N/A')" +} + +disk_info() { + print_header "Disk Usage (Top 5 by Size)" + echo "Filesystem Size Used Avail Use% Mounted On" + df -h --output=source,size,used,avail,pcent,target 2>/dev/null | \ + tail -n +2 | sort -k2 -rh | head -5 || \ + df -h | tail -n +2 | head -5 +} + +memory_info() { + print_header "Memory Usage" + free -h +} + +top_cpu_processes() { + print_header "Top 5 CPU-Consuming Processes" + printf "%-8s %-10s %-6s %-6s %s\n" "PID" "USER" "CPU%" "MEM%" "COMMAND" + ps aux --sort=-%cpu 2>/dev/null | \ + awk 'NR>1 {printf "%-8s %-10s %-6s %-6s %s\n", $2, $1, $3, $4, $11}' | head -5 +} + +main() { + echo "" + echo " *** SYSTEM INFO REPORT ***" + echo " Generated: $(date '+%Y-%m-%d %H:%M:%S')" + + host_info + uptime_info + disk_info + memory_info + top_cpu_processes + + echo "" + echo "$SEPARATOR" + echo " End of Report" + echo "$SEPARATOR" + echo "" +} + +main +``` + +### Output + +``` + *** SYSTEM INFO REPORT *** + Generated: 2026-02-25 07:11:46 + +============================================== + Hostname & OS Info +============================================== +Hostname : runsc +OS : GNU/Linux +Kernel : 4.4.0 +Arch : x86_64 +Distro : Ubuntu 24.04.4 LTS + +============================================== + Uptime +============================================== +up 0 minutes +Boot time : Feb 25 + +============================================== + Disk Usage (Top 5 by Size) +============================================== +Filesystem Size Used Avail Use% Mounted On +none 1.0P 0 1.0P 0% /mnt/user-data/uploads +... + +============================================== + Memory Usage +============================================== + total used free shared buff/cache available +Mem: 9.0Gi 13Mi 9.0Gi 0B 9.7Mi 9.0Gi +Swap: 0B 0B 0B + +============================================== + Top 5 CPU-Consuming Processes +============================================== +PID USER CPU% MEM% COMMAND +78 root 87.5 0.0 ps +80 root 12.5 0.0 head +... + +============================================== + End of Report +============================================== +``` + +--- + +## Understanding `set -euo pipefail` + +The combination `set -euo pipefail` is considered the standard "strict mode" for Bash scripting. It catches three major categories of silent failures: + +**`set -e`** stops scripts from blindly continuing after a command fails. Without it, a script could fail halfway through — say, while creating a deployment artifact — and silently proceed to the next step, causing corrupted or incomplete work. + +**`set -u`** catches the extremely common bug of a typo in a variable name. Without it, `$CONFIIG_PATH` (typo for `$CONFIG_PATH`) would silently expand to an empty string, causing confusing downstream errors. With `-u`, the script exits immediately with a clear error message. + +**`set -o pipefail`** solves the problem that Bash only checks the exit code of the *last* command in a pipeline. The classic footgun: `grep "pattern" file.txt | wc -l` — if the file doesn't exist, `grep` fails but `wc -l` succeeds (returning `0`), so the whole pipeline exits 0. With `pipefail`, the pipeline correctly reports failure. + +--- + +## What I Learned — 3 Key Points + +**1. Functions make scripts composable and testable.** +Breaking logic into functions means each piece can be understood, tested, and reused independently. A `main()` function that calls named functions reads almost like documentation — you can understand a 200-line script just by reading `main()`. + +**2. Always use `local` in functions — no exceptions.** +Without `local`, every variable in a function is a potential landmine for every other function and global scope. The habit of typing `local` first is cheap; debugging a variable collision at 2am is not. + +**3. `set -euo pipefail` is not optional for production scripts.** +Silent failures are the hardest bugs to diagnose. A script that exits loudly when something goes wrong is infinitely better than one that silently corrupts state. Treat strict mode as the default, not an extra. + +--- + +## File Structure + +``` +2026/day-18/ +├── functions.sh # Task 1: Basic functions +├── disk_check.sh # Task 2: Functions with return values +├── strict_demo.sh # Task 3: Strict mode demonstration +├── local_demo.sh # Task 4: Local variables +├── system_info.sh # Task 5: Full system info reporter +└── day-18-scripting.md # This documentation file +``` + +--- + +*Part of the #90DaysOfDevOps challenge — Day 18* +*#DevOpsKaJosh #TrainWithShubham* \ No newline at end of file diff --git a/2026/day-18/zookeper.log b/2026/day-18/zookeper.log new file mode 100644 index 0000000000..74c71dda07 --- /dev/null +++ b/2026/day-18/zookeper.log @@ -0,0 +1,2000 @@ +2015-07-29 17:41:44,747 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 3200 +2015-07-29 19:04:12,394 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:45307 +2015-07-29 19:04:29,071 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:04:29,079 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:13:17,524 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:13:24,282 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:13:24,370 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:57707 +2015-07-29 19:13:27,721 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:13:34,382 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:13:37,626 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:13:44,301 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:13:47,731 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:13:54,220 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:45382 +2015-07-29 19:13:54,399 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:14:04,406 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:14:07,559 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:14:07,653 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:14:24,329 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:14:37,585 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:14:44,256 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:45440 +2015-07-29 19:14:47,593 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:14:54,354 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:15:24,476 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:15:37,647 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:15:37,648 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:15:54,407 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:15:57,854 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:57895 +2015-07-29 19:16:04,412 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:16:04,414 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:16:07,659 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:16:14,520 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:16:24,348 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:16:27,865 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:16:27,865 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:16:34,433 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:16:44,440 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:47727 +2015-07-29 19:16:57,707 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:17:17,721 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:17:17,921 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:17:24,471 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:17:24,477 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:17:57,741 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:17:57,939 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:58035 +2015-07-29 19:17:57,955 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:18:04,430 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:18:07,748 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:18:07,756 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:18:14,511 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:47838 +2015-07-29 19:18:14,839 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:18:34,635 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:18:37,770 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:18:47,785 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:18:54,534 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:18:54,534 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:18:57,988 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:19:04,661 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:58116 +2015-07-29 19:21:36,502 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:45957 +2015-07-29 19:21:36,607 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:21:39,846 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:21:39,846 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:21:43,389 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:21:46,525 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:21:46,537 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:21:46,728 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:58303 +2015-07-29 19:21:49,960 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:48096 +2015-07-29 19:21:53,209 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:21:53,220 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:21:53,410 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:21:53,412 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:21:53,414 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:21:56,644 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:21:56,756 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:21:59,997 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:22:03,324 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:48141 +2015-07-29 19:22:03,337 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:22:03,439 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:22:10,020 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:22:13,256 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:22:13,257 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:22:16,799 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:22:20,143 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:58421 +2015-07-29 19:22:23,289 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:22:23,378 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:22:23,379 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:22:26,617 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:46128 +2015-07-29 19:22:26,618 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:22:26,634 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:22:26,734 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:22:26,829 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:22:26,830 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:58452 +2015-07-29 19:22:29,975 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:22:33,313 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:22:33,513 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:22:36,642 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:22:36,659 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:46173 +2015-07-29 19:22:36,659 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:22:40,083 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:48280 +2015-07-29 19:22:43,421 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:22:43,536 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:22:46,680 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:22:50,025 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:22:53,441 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:22:53,462 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:22:56,689 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:22:56,892 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:23:00,124 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:23:00,131 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:23:00,237 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:58565 +2015-07-29 19:23:03,387 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:23:03,464 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:23:03,590 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:23:06,729 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:23:13,491 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:23:13,596 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:23:16,755 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:23:16,848 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:48413 +2015-07-29 19:23:16,937 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:23:20,094 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:46329 +2015-07-29 19:23:20,095 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:23:20,173 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:23:20,278 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:23:23,518 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:23:26,760 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:23:26,979 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:23:30,110 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:46360 +2015-07-29 19:23:30,116 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:23:30,320 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:23:33,457 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:23:33,553 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:23:36,783 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:23:40,140 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:23:46,827 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:46424 +2015-07-29 19:23:46,830 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:23:46,917 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:23:50,171 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:23:53,488 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:46440 +2015-07-29 19:23:56,838 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:23:56,851 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:24:00,386 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:24:03,616 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:24:03,725 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:24:07,062 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:24:10,216 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:24:10,286 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:48600 +2015-07-29 19:24:13,542 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:24:13,553 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:46519 +2015-07-29 19:24:16,883 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:24:16,987 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:24:20,217 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:24:20,413 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:24:20,431 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:24:23,563 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:46552 +2015-07-29 19:24:23,574 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:24:23,578 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:24:30,451 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:24:36,927 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:24:37,012 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:24:40,383 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:24:43,814 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:24:50,301 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:24:50,374 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:24:57,160 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:24:57,175 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:25:03,663 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:25:03,744 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:25:03,857 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:59016 +2015-07-29 19:25:07,003 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:25:07,079 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:25:07,102 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:25:07,107 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:48811 +2015-07-29 19:25:10,536 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:59037 +2015-07-29 19:25:10,539 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:25:13,695 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:25:13,874 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:25:17,021 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:25:17,124 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:25:23,702 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:25:23,811 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:25:23,889 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:59078 +2015-07-29 19:25:27,058 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:25:27,242 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:25:30,398 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:46798 +2015-07-29 19:25:30,571 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:25:33,833 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:25:33,923 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:25:37,062 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:46812 +2015-07-29 19:25:37,065 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:25:37,257 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:59130 +2015-07-29 19:25:37,259 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:25:40,484 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:48922 +2015-07-29 19:25:40,600 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:25:43,751 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:25:47,102 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:25:47,195 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:25:50,507 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:25:50,537 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:25:50,615 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:27:55,066 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:47327 +2015-07-29 19:27:58,407 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:27:58,827 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:47351 +2015-07-29 19:28:02,167 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:47366 +2015-07-29 19:28:05,197 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:28:08,431 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:47390 +2015-07-29 19:28:08,636 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:59614 +2015-07-29 19:28:12,190 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:28:15,221 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:28:18,656 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:28:18,661 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:28:21,796 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:28:21,902 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:28:21,902 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:28:22,000 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:28:28,473 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:47472 +2015-07-29 19:28:31,823 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:28:32,018 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:59689 +2015-07-29 19:28:35,160 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:28:35,361 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:59706 +2015-07-29 19:28:38,703 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:59722 +2015-07-29 19:28:38,704 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:28:41,841 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:28:41,844 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:47540 +2015-07-29 19:28:42,254 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:28:48,527 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:47571 +2015-07-29 19:28:55,309 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:28:58,547 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:47615 +2015-07-29 19:29:01,988 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:49588 +2015-07-29 19:29:08,571 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:29:08,668 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:49610 +2015-07-29 19:29:08,669 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:29:08,670 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:29:08,671 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:29:12,009 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:29:12,115 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:29:12,115 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:29:12,116 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:29:15,349 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:29:15,349 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:29:15,353 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:29:18,798 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:29:21,933 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:29:22,033 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:29:22,136 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:29:22,340 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:29:25,274 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:29:28,612 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:29:28,820 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:29:29,020 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:29:32,056 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:29:35,500 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:59925 +2015-07-29 19:29:38,840 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:29:38,841 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:29:38,843 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:29:42,070 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:29:42,075 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:29:45,414 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:29:45,522 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:29:52,202 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:29:55,545 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:29:58,673 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:29:58,774 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:29:58,778 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:29:58,779 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:29:58,884 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:30:02,019 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:47885 +2015-07-29 19:30:02,117 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:49806 +2015-07-29 19:30:05,458 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:30:08,802 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:30:12,246 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:30:15,382 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:30:15,586 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:60070 +2015-07-29 19:30:18,723 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:30:22,162 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:30:25,405 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:30:25,608 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:30:25,608 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:30:25,609 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:30:35,630 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:30:38,760 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:30:38,863 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:49940 +2015-07-29 19:30:42,315 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:30:42,315 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:30:45,653 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:30:48,785 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:30:48,883 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:30:48,997 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:30:59,011 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:31:02,142 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:31:02,243 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:31:02,243 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:31:02,352 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:31:02,353 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:31:05,483 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:31:05,583 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:31:08,823 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:31:08,922 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:50043 +2015-07-29 19:31:15,504 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:31:32,214 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:31:32,214 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:31:32,420 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:31:35,546 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:31:35,760 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:31:39,093 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:31:39,095 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:60366 +2015-07-29 19:31:45,780 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:31:49,006 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:31:49,116 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:31:49,117 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:31:52,349 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:31:52,456 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:31:52,456 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:31:55,588 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:31:55,590 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:48289 +2015-07-29 19:31:55,592 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:31:55,793 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:60423 +2015-07-29 19:31:55,805 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:31:58,932 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:31:59,141 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:32:02,269 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:32:02,363 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:32:02,367 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:32:05,705 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:32:08,955 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:32:09,163 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:32:12,495 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:32:12,503 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:60489 +2015-07-29 19:32:15,845 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:32:18,976 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:32:22,405 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:32:22,525 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:32:25,653 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:32:25,748 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:32:29,085 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:50332 +2015-07-29 19:32:29,085 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:32:32,336 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:32:32,428 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:32:35,678 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:32:35,764 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:50354 +2015-07-29 19:32:39,216 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:32:42,355 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:32:42,357 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:32:42,443 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:32:42,557 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:32:49,036 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:32:49,042 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:48503 +2015-07-29 19:32:49,237 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:32:52,469 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:32:59,143 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:50434 +2015-07-29 19:33:02,398 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:33:02,398 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:48563 +2015-07-29 19:33:02,597 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:33:05,829 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:33:09,080 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:33:09,170 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:33:12,423 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:48609 +2015-07-29 19:33:12,618 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:33:12,627 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:33:13,727 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:48612 +2015-07-29 19:33:13,728 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:33:15,851 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:33:15,853 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:33:15,963 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:33:15,965 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:60717 +2015-07-29 19:33:19,190 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:33:19,298 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:33:19,303 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:60726 +2015-07-29 19:33:22,441 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:33:22,532 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:50526 +2015-07-29 19:33:23,749 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:33:25,872 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:33:25,873 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:33:25,983 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:60750 +2015-07-29 19:33:29,118 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:33:29,212 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:33:29,212 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:50546 +2015-07-29 19:33:29,326 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:33:32,459 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:33:32,552 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:33:35,800 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:33:35,894 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:33:39,140 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:33:39,344 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:33:42,574 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:33:42,575 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:50597 +2015-07-29 19:33:42,678 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:33:42,688 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:33:45,916 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:33:46,025 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:33:46,026 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:33:49,162 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:33:49,364 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:60834 +2015-07-29 19:33:52,594 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:33:52,595 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:50633 +2015-07-29 19:33:55,843 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:33:55,844 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:33:55,935 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:33:59,385 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:34:02,725 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:34:05,861 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:34:05,862 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:48814 +2015-07-29 19:34:05,863 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:34:05,863 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:48817 +2015-07-29 19:34:05,958 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:34:06,067 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:34:09,294 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:34:09,294 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:34:09,295 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:34:12,634 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:34:12,742 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:34:12,745 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:60918 +2015-07-29 19:34:12,747 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:34:15,884 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:34:15,884 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:34:16,089 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:34:26,102 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:34:29,246 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:34:29,447 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:34:29,448 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:60984 +2015-07-29 19:34:32,782 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:34:32,788 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:60996 +2015-07-29 19:34:39,358 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:34:42,809 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:34:46,038 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:34:46,038 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:34:49,487 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:34:52,717 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:50849 +2015-07-29 19:34:55,969 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:49023 +2015-07-29 19:35:02,651 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:35:02,846 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:35:05,992 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:35:06,078 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:35:09,326 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:35:09,526 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:32891 +2015-07-29 19:35:16,098 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:35:16,207 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:35:19,443 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:35:19,544 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:32924 +2015-07-29 19:35:22,888 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:35:29,368 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:35:29,372 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:35:29,458 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:35:36,142 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:35:42,928 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:33010 +2015-07-29 19:35:46,073 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:49204 +2015-07-29 19:35:49,417 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:35:49,417 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:35:49,498 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:51050 +2015-07-29 19:35:52,756 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:35:52,842 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:35:56,178 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:35:56,180 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:36:02,861 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:51104 +2015-07-29 19:36:06,119 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:36:09,456 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:36:09,645 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:36:16,136 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:36:16,221 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:36:16,331 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:36:16,334 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:36:19,480 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:36:22,816 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:36:22,901 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:36:22,902 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:36:26,155 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:36:26,156 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:36:26,157 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:36:26,349 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:33165 +2015-07-29 19:36:29,686 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:36:32,920 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:36:33,030 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:36:36,365 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:33198 +2015-07-29 19:36:36,370 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:36:39,516 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:36:39,597 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:36:42,859 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:36:42,939 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:36:43,049 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:33225 +2015-07-29 19:36:43,054 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:36:49,620 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:36:49,623 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:36:49,730 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:33250 +2015-07-29 19:36:49,735 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:33255 +2015-07-29 19:36:52,879 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:36:53,074 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:33266 +2015-07-29 19:36:56,220 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:36:56,302 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:51296 +2015-07-29 19:36:56,303 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:36:59,746 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:33282 +2015-07-29 19:37:02,901 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:37:09,774 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:37:12,919 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:37:12,920 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:49518 +2015-07-29 19:37:13,114 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:37:19,676 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:37:19,683 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:51380 +2015-07-29 19:52:04,792 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.18:42772 which had sessionid 0x14ed93111f20005 +2015-07-29 19:52:05,118 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-29 19:52:09,519 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.12:45542 which had sessionid 0x14ed93111f20002 +2015-07-29 19:54:13,615 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@832] - Client attempting to renew session 0x24ed93119420016 at /10.10.34.13:37115 +2015-07-29 19:54:45,337 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.13:37106 which had sessionid 0x14ed93111f20010 +2015-07-29 21:01:41,504 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.19:33425 +2015-07-29 21:34:45,452 - INFO [CommitProcessor:1:ZooKeeperServer@595] - Established session 0x14ed93111f20027 with negotiated timeout 10000 for client /10.10.34.13:37177 +2015-07-29 21:34:48,285 - INFO [CommitProcessor:1:ZooKeeperServer@595] - Established session 0x14ed93111f2002b with negotiated timeout 10000 for client /10.10.34.22:47073 +2015-07-29 21:39:24,986 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.13:37196 +2015-07-29 21:39:28,234 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.26:56952 +2015-07-29 23:44:21,576 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.11:49557 which had sessionid 0x14ed93111f20048 +2015-07-29 23:44:28,903 - ERROR [CommitProcessor:1:NIOServerCnxn@180] - Unexpected Exception: +2015-07-29 23:52:08,962 - INFO [CommitProcessor:1:ZooKeeperServer@595] - Established session 0x14ed93111f2005b with negotiated timeout 10000 for client /10.10.34.28:52117 +2015-07-29 23:52:09,163 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.30:38562 +2015-07-29 23:52:09,783 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.36:32876 +2015-07-29 23:52:09,785 - INFO [CommitProcessor:1:ZooKeeperServer@595] - Established session 0x14ed93111f2005f with negotiated timeout 10000 for client /10.10.34.36:32876 +2015-07-30 13:47:25,927 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.11:45997 +2015-07-30 14:42:40,474 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.11:49346 +2015-07-30 14:47:15,835 - INFO [CommitProcessor:1:ZooKeeperServer@595] - Established session 0x14ed93111f20079 with negotiated timeout 20000 for client /10.10.34.11:49800 +2015-07-30 14:52:21,906 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.29:39382 which had sessionid 0x14ed93111f2005d +2015-07-30 14:52:36,477 - INFO [CommitProcessor:1:ZooKeeperServer@595] - Established session 0x14ed93111f2007c with negotiated timeout 10000 for client /10.10.34.11:50276 +2015-07-30 14:53:21,340 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.11:50286 +2015-07-30 15:00:24,824 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.11:50301 +2015-07-30 15:00:24,825 - INFO [CommitProcessor:1:ZooKeeperServer@595] - Established session 0x14ed93111f20082 with negotiated timeout 10000 for client /10.10.34.11:50301 +2015-07-30 15:23:21,827 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.11:50402 +2015-07-30 15:35:04,462 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.20:56414 +2015-07-30 15:41:40,669 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.11:50940 which had sessionid 0x14ed93111f20099 +2015-07-30 16:09:17,019 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.11:52893 which had sessionid 0x14ed93111f2009b +2015-07-30 16:12:01,554 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.19:33442; will be dropped if server is in r-o mode +2015-07-30 16:12:02,180 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.29:39387 +2015-07-30 16:18:34,053 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.11:53821 +2015-07-30 16:18:34,149 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.12:45668 +2015-07-30 16:18:36,818 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.20:56418; will be dropped if server is in r-o mode +2015-07-30 16:18:38,680 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.42:34164; will be dropped if server is in r-o mode +2015-07-30 16:21:28,258 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.12:45675 +2015-07-30 16:34:50,091 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.11:54411; will be dropped if server is in r-o mode +2015-07-30 16:44:26,593 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.12:45682 which had sessionid 0x14ed93111f200cd +2015-07-30 16:44:36,930 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.13:37454; will be dropped if server is in r-o mode +2015-07-30 17:06:34,257 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.12:45697 which had sessionid 0x14ed93111f200d6 +2015-07-30 17:06:40,616 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.11:54632 +2015-07-30 17:06:40,816 - INFO [CommitProcessor:1:ZooKeeperServer@595] - Established session 0x14ed93111f200df with negotiated timeout 10000 for client /10.10.34.13:37467 +2015-07-30 17:11:54,937 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-30 17:13:32,714 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.11:54738 +2015-07-30 17:22:34,245 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-30 17:36:31,976 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.11:54983 which had sessionid 0x14ed93111f200f0 +2015-07-30 17:43:58,186 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:Environment@100] - Server environment:user.dir=/ +2015-07-30 17:49:05,943 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.12:45728; will be dropped if server is in r-o mode +2015-07-30 17:55:26,200 - WARN [WorkerSender[myid=1]:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-07-30 18:18:01,981 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.12:43125 +2015-07-30 18:18:02,003 - INFO [ProcessThread(sid:1 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x14ede63a5a70002 +2015-07-30 18:18:30,005 - INFO [ProcessThread(sid:1 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x34ede65503f0010 +2015-07-30 19:50:21,400 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-30 19:50:32,001 - INFO [ProcessThread(sid:1 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x14ede63a5a70023 +2015-07-30 19:59:02,538 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.13:38053; will be dropped if server is in r-o mode +2015-07-30 19:59:08,004 - INFO [ProcessThread(sid:1 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x34ede65503f002b +2015-07-30 20:06:34,001 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x24ede63a01b003b, timeout of 10000ms exceeded +2015-07-30 20:06:34,003 - INFO [ProcessThread(sid:1 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x24ede63a01b003b +2015-07-30 20:13:46,001 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x34ede65503f0036, timeout of 10000ms exceeded +2015-07-30 20:13:46,004 - INFO [ProcessThread(sid:1 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x34ede65503f0039 +2015-07-30 20:17:12,294 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-30 20:34:58,003 - INFO [ProcessThread(sid:1 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x14ede63a5a7003a +2015-07-30 20:35:02,324 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.13:38079; will be dropped if server is in r-o mode +2015-07-30 21:03:35,465 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-30 21:03:35,468 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.13:38088 which had sessionid 0x14ede63a5a70048 +2015-07-30 21:03:44,632 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.11:40489; will be dropped if server is in r-o mode +2015-07-30 21:03:44,634 - INFO [CommitProcessor:1:ZooKeeperServer@595] - Established session 0x14ede63a5a7004b with negotiated timeout 10000 for client /10.10.34.11:40489 +2015-07-30 21:03:47,578 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.21:37904 +2015-07-30 23:03:42,133 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.17:51214 which had sessionid 0x14ede63a5a70053 +2015-07-30 23:03:52,001 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x34ede65503f005c, timeout of 10000ms exceeded +2015-07-30 23:03:54,002 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x24ede63a01b0062, timeout of 10000ms exceeded +2015-07-30 23:43:22,414 - WARN [LearnerHandler-/10.10.34.12:35276:LearnerHandler@575] - ******* GOODBYE /10.10.34.12:35276 ******** +2015-07-30 23:43:23,613 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumPeer@670] - LOOKING +2015-07-30 23:44:01,784 - WARN [WorkerSender[myid=1]:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-07-30 23:44:04,784 - WARN [WorkerSender[myid=1]:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-07-30 23:44:58,183 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-07-30 23:49:40,005 - WARN [RecvWorker:3:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-30 23:52:26,272 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-07-31 00:02:57,202 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.40:40996; will be dropped if server is in r-o mode +2015-07-31 00:17:52,585 - INFO [CommitProcessor:1:ZooKeeperServer@595] - Established session 0x14edfaa86f60013 with negotiated timeout 10000 for client /10.10.34.27:44600 +2015-07-31 00:19:18,655 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-31 00:19:19,582 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-31 00:19:37,018 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.16:39498; will be dropped if server is in r-o mode +2015-07-31 11:01:40,975 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.13:54485 which had sessionid 0x14edfaa86f60021 +2015-07-31 11:01:54,714 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.12:34568 +2015-07-31 11:01:57,854 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.25:58975; will be dropped if server is in r-o mode +2015-07-31 11:09:01,762 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.33:39730; will be dropped if server is in r-o mode +2015-07-31 15:31:40,971 - INFO [Thread-1:QuorumCnxManager$Listener@486] - My election bind port: 0.0.0.0/0.0.0.0:3888 +2015-07-31 15:31:40,999 - INFO [WorkerSender[myid=1]:QuorumCnxManager@190] - Have smaller server identifier, so dropping the connection: (2, 1) +2015-07-31 15:31:42,213 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumPeer@738] - FOLLOWING +2015-07-31 15:33:29,640 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-07-31 19:30:07,398 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumPeer@670] - LOOKING +2015-07-31 19:30:07,403 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@740] - New election. My id = 1, proposed zxid=0x700000000 +2015-07-31 19:30:07,445 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:Environment@100] - Server environment:host.name=mesos-master-1 +2015-07-31 19:30:07,452 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:Follower@63] - FOLLOWING - LEADER ELECTION TOOK - 49 +2015-07-31 21:11:05,474 - INFO [CommitProcessor:1:ZooKeeperServer@595] - Established session 0x14ee3e057ed000c with negotiated timeout 10000 for client /10.10.34.37:49834 +2015-07-31 21:23:08,968 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.11:40061 +2015-07-31 21:23:08,969 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.11:40061 +2015-07-31 21:23:10,926 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.13:39525; will be dropped if server is in r-o mode +2015-07-31 21:23:12,897 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.35:48971; will be dropped if server is in r-o mode +2015-07-31 21:24:43,960 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-31 21:32:18,390 - INFO [CommitProcessor:1:ZooKeeperServer@595] - Established session 0x14ee3e057ed002c with negotiated timeout 10000 for client /10.10.34.19:43049 +2015-07-31 21:32:20,131 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.40:58713 +2015-07-31 21:44:41,270 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.12:59661 which had sessionid 0x14ee3e057ed0027 +2015-08-07 07:27:47,425 - INFO [WorkerReceiver[myid=1]:FastLeaderElection@542] - Notification: 3 (n.leader), 0x700000197 (n.zxid), 0x1 (n.round), LEADING (n.state), 3 (n.sid), 0x7 (n.peerEPoch), LOOKING (my state) +2015-08-07 07:27:47,650 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:Follower@63] - FOLLOWING - LEADER ELECTION TOOK - 238 +2015-08-10 17:52:39,654 - INFO [CommitProcessor:1:ZooKeeperServer@595] - Established session 0x14f05578bd80002 with negotiated timeout 10000 for client /10.10.34.12:46262 +2015-08-10 17:53:06,869 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-08-10 17:53:22,767 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.15:54175 +2015-08-10 17:53:22,870 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.16:40418; will be dropped if server is in r-o mode +2015-08-10 18:12:23,970 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.19:57338 which had sessionid 0x14f05578bd8000d +2015-08-10 18:12:24,076 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-08-10 18:12:24,375 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-08-10 18:13:25,200 - INFO [CommitProcessor:1:ZooKeeperServer@595] - Established session 0x14f05578bd80020 with negotiated timeout 10000 for client /10.10.34.11:38390 +2015-08-10 18:23:49,901 - INFO [main:DatadirCleanupManager@78] - autopurge.snapRetainCount set to 3 +2015-08-10 18:23:50,332 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:Environment@100] - Server environment:java.vendor=Oracle Corporation +2015-08-10 18:23:52,646 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:Learner@107] - Revalidating client: 0x14f05578bd80018 +2015-08-10 18:23:52,649 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:ZooKeeperServer@595] - Established session 0x14f05578bd80016 with negotiated timeout 10000 for client /10.10.34.13:38490 +2015-08-10 18:23:52,650 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:ZooKeeperServer@595] - Established session 0x14f05578bd80013 with negotiated timeout 10000 for client /10.10.34.11:38530 +2015-08-10 18:23:52,653 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@832] - Client attempting to renew session 0x14f05578bd8001b at /10.10.34.20:56374 +2015-08-10 18:25:22,080 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:Environment@100] - Server environment:zookeeper.version=3.4.5--1, built on 06/10/2013 17:26 GMT +2015-08-10 18:25:22,082 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:Environment@100] - Server environment:user.name=zookeeper +2015-08-10 18:25:24,332 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:Learner@107] - Revalidating client: 0x14f05578bd80013 +2015-08-10 18:25:39,907 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-08-10 18:27:49,007 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.12:46331 which had sessionid 0x14f1724a6e80004 +2015-08-18 16:09:13,285 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:34051 +2015-08-18 16:09:15,099 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:Environment@100] - Server environment:os.name=Linux +2015-08-20 13:28:51,889 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.11:54839 +2015-08-20 13:28:51,983 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.12:58349 +2015-08-20 17:12:29,467 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.11:56471 (no session established for client) +2015-08-20 17:14:11,414 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@354] - Exception causing close of session 0x0 due to java.io.IOException: ZooKeeperServer not running +2015-08-20 17:14:12,326 - INFO [WorkerReceiver[myid=1]:FastLeaderElection@542] - Notification: 2 (n.leader), 0xb00000084 (n.zxid), 0x2 (n.round), LOOKING (n.state), 1 (n.sid), 0xb (n.peerEPoch), LOOKING (my state) +2015-08-20 17:14:23,824 - INFO [WorkerReceiver[myid=1]:FastLeaderElection@542] - Notification: 3 (n.leader), 0xb0000007b (n.zxid), 0x2 (n.round), LOOKING (n.state), 3 (n.sid), 0xb (n.peerEPoch), FOLLOWING (my state) +2015-08-20 17:22:22,288 - INFO [CommitProcessor:1:ZooKeeperServer@595] - Established session 0x14f4a6318b80005 with negotiated timeout 10000 for client /10.10.34.11:56492 +2015-08-20 17:24:06,873 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.12:58913 +2015-08-20 17:24:07,582 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.18:36934 +2015-08-20 17:24:07,816 - INFO [CommitProcessor:1:ZooKeeperServer@595] - Established session 0x14f4a6318b80013 with negotiated timeout 10000 for client /10.10.34.20:43137 +2015-08-20 19:02:23,456 - INFO [CommitProcessor:1:ZooKeeperServer@595] - Established session 0x14f4a6318b80022 with negotiated timeout 10000 for client /10.10.34.30:43272 +2015-08-20 19:32:55,963 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.35:48997 which had sessionid 0x14f4a6318b80024 +2015-08-20 19:33:02,860 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-08-20 19:33:02,860 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.12:58917 which had sessionid 0x14f4a6318b80018 +2015-08-21 15:55:04,347 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.13:50545; will be dropped if server is in r-o mode +2015-08-21 15:55:07,600 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.30:43278 +2015-08-21 15:55:14,153 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.14:46136 +2015-08-24 15:26:54,494 - INFO [main:QuorumPeer@913] - tickTime set to 2000 +2015-08-24 15:27:03,681 - WARN [WorkerSender[myid=1]:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-24 15:29:13,641 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-24 15:36:13,663 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-24 15:37:13,664 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-24 15:51:13,708 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-24 15:55:13,717 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-24 15:57:13,723 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-24 16:02:13,739 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-24 16:03:13,740 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-24 16:11:13,765 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-24 16:12:13,767 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-24 16:37:13,837 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-24 16:51:13,876 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-24 17:29:13,977 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-24 17:39:14,002 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-24 18:02:14,063 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-24 18:04:14,068 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-24 18:28:14,133 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-24 18:31:14,142 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-24 18:41:14,170 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-24 18:47:14,187 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-24 18:51:14,196 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-24 19:01:14,221 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-24 19:05:14,230 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-24 19:09:14,240 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-24 19:19:14,265 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-24 19:31:14,292 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-24 19:45:14,327 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-24 19:55:14,351 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-24 20:01:14,364 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-24 20:16:14,399 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-24 20:56:14,493 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-24 20:57:14,495 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-24 21:07:14,519 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-24 21:11:14,529 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-24 21:26:14,562 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-24 22:04:14,650 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-24 22:08:14,659 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-24 22:09:14,662 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-24 22:10:14,663 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-24 22:16:14,677 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-24 22:17:14,678 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-24 22:25:14,698 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-24 22:32:14,713 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-24 22:39:14,728 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-24 22:42:14,733 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-24 22:45:14,741 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-24 22:48:14,746 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-24 22:49:14,750 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-24 22:57:14,766 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-24 23:04:14,782 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-24 23:09:14,792 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-24 23:25:14,825 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-24 23:26:14,827 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-24 23:38:14,850 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-24 23:58:14,891 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-25 00:00:14,897 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-25 00:14:14,924 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-25 00:23:14,943 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-25 00:26:14,949 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-25 00:28:14,953 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-25 00:42:14,982 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-25 00:44:14,985 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-25 01:12:15,044 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-25 01:45:15,113 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-25 01:47:15,116 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-25 02:06:15,155 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-25 02:09:15,162 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-25 02:36:15,217 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-25 02:54:15,254 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-25 02:56:15,258 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-25 03:16:15,297 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-25 03:28:15,323 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-25 03:29:15,325 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-25 03:30:15,327 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-25 03:33:15,333 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-25 03:38:15,343 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-25 03:54:15,375 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-25 04:10:15,407 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-25 04:14:15,416 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-25 04:21:15,429 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-25 04:28:15,443 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-25 05:00:15,508 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-25 05:08:15,525 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-25 05:09:15,527 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-25 05:46:15,601 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-25 05:50:15,608 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-25 05:58:15,624 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-25 05:58:15,626 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-25 06:41:15,711 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-25 06:58:15,745 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-25 07:03:15,756 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-25 07:04:15,757 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-25 07:04:15,758 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-25 07:16:15,781 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-25 07:27:15,803 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-25 08:20:15,909 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-25 08:21:15,911 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-25 08:23:15,916 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-25 08:28:15,925 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-25 08:29:15,928 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-25 08:33:15,936 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-25 08:49:15,968 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-25 09:09:16,008 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-25 09:11:16,012 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-25 09:16:16,022 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-25 09:19:16,027 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-25 09:24:16,037 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-25 10:13:16,137 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-25 10:14:16,139 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-25 10:42:16,195 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-25 10:50:16,211 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-25 11:03:16,237 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-25 11:20:12,465 - WARN [RecvWorker:3:QuorumCnxManager$RecvWorker@762] - Connection broken for id 3, my id = 1, error = +2015-08-25 11:21:22,561 - WARN [WorkerSender[myid=1]:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-07-29 17:42:30,405 - INFO [QuorumPeer[myid=2]/0:0:0:0:0:0:0:0:2181:Environment@100] - Server environment:java.vendor=Oracle Corporation +2015-07-29 19:03:35,413 - ERROR [LearnerHandler-/10.10.34.11:52225:LearnerHandler@562] - Unexpected exception causing shutdown while sock still open +2015-07-29 19:03:54,584 - ERROR [LearnerHandler-/10.10.34.11:52241:LearnerHandler@562] - Unexpected exception causing shutdown while sock still open +2015-07-29 19:04:30,989 - WARN [LearnerHandler-/10.10.34.11:52264:LearnerHandler@575] - ******* GOODBYE /10.10.34.11:52264 ******** +2015-07-29 19:04:30,989 - ERROR [LearnerHandler-/10.10.34.11:52265:LearnerHandler@562] - Unexpected exception causing shutdown while sock still open +2015-07-29 19:04:40,999 - ERROR [LearnerHandler-/10.10.34.11:52273:LearnerHandler@562] - Unexpected exception causing shutdown while sock still open +2015-07-29 19:13:46,128 - WARN [LearnerHandler-/10.10.34.11:52308:LearnerHandler@575] - ******* GOODBYE /10.10.34.11:52308 ******** +2015-07-29 19:14:06,236 - WARN [LearnerHandler-/10.10.34.12:59060:LearnerHandler@575] - ******* GOODBYE /10.10.34.12:59060 ******** +2015-07-29 19:14:46,264 - WARN [LearnerHandler-/10.10.34.12:59103:LearnerHandler@575] - ******* GOODBYE /10.10.34.12:59103 ******** +2015-07-29 19:14:56,371 - WARN [LearnerHandler-/10.10.34.13:57247:LearnerHandler@575] - ******* GOODBYE /10.10.34.13:57247 ******** +2015-07-29 19:15:16,204 - ERROR [LearnerHandler-/10.10.34.11:52419:LearnerHandler@562] - Unexpected exception causing shutdown while sock still open +2015-07-29 19:15:56,423 - WARN [LearnerHandler-/10.10.34.13:57319:LearnerHandler@575] - ******* GOODBYE /10.10.34.13:57319 ******** +2015-07-29 19:16:06,243 - WARN [LearnerHandler-/10.10.34.11:52476:LearnerHandler@575] - ******* GOODBYE /10.10.34.11:52476 ******** +2015-07-29 19:16:06,336 - WARN [LearnerHandler-/10.10.34.12:59203:LearnerHandler@575] - ******* GOODBYE /10.10.34.12:59203 ******** +2015-07-29 19:16:16,339 - WARN [LearnerHandler-/10.10.34.12:59211:LearnerHandler@575] - ******* GOODBYE /10.10.34.12:59211 ******** +2015-07-29 19:16:26,268 - WARN [LearnerHandler-/10.10.34.11:52502:LearnerHandler@575] - ******* GOODBYE /10.10.34.11:52502 ******** +2015-07-29 19:16:26,447 - ERROR [LearnerHandler-/10.10.34.13:57354:LearnerHandler@562] - Unexpected exception causing shutdown while sock still open +2015-07-29 19:17:36,507 - ERROR [LearnerHandler-/10.10.34.13:57438:LearnerHandler@562] - Unexpected exception causing shutdown while sock still open +2015-07-29 19:17:56,522 - WARN [LearnerHandler-/10.10.34.13:57458:LearnerHandler@575] - ******* GOODBYE /10.10.34.13:57458 ******** +2015-07-29 19:18:26,565 - WARN [LearnerHandler-/10.10.34.13:57502:LearnerHandler@575] - ******* GOODBYE /10.10.34.13:57502 ******** +2015-07-29 19:18:56,377 - WARN [LearnerHandler-/10.10.34.11:52703:LearnerHandler@575] - ******* GOODBYE /10.10.34.11:52703 ******** +2015-07-29 19:18:56,457 - WARN [LearnerHandler-/10.10.34.12:59406:LearnerHandler@575] - ******* GOODBYE /10.10.34.12:59406 ******** +2015-07-29 19:20:16,690 - ERROR [LearnerHandler-/10.10.34.12:59455:LearnerHandler@562] - Unexpected exception causing shutdown while sock still open +2015-07-29 19:20:16,794 - WARN [LearnerHandler-/10.10.34.13:57580:LearnerHandler@575] - ******* GOODBYE /10.10.34.13:57580 ******** +2015-07-29 19:20:36,704 - ERROR [LearnerHandler-/10.10.34.12:59480:LearnerHandler@562] - Unexpected exception causing shutdown while sock still open +2015-07-29 19:20:46,814 - ERROR [LearnerHandler-/10.10.34.13:57617:LearnerHandler@562] - Unexpected exception causing shutdown while sock still open +2015-07-29 19:20:56,605 - ERROR [LearnerHandler-/10.10.34.11:52814:LearnerHandler@562] - Unexpected exception causing shutdown while sock still open +2015-07-29 19:20:56,608 - WARN [LearnerHandler-/10.10.34.11:52818:LearnerHandler@575] - ******* GOODBYE /10.10.34.11:52818 ******** +2015-07-29 19:21:16,619 - WARN [LearnerHandler-/10.10.34.11:52844:LearnerHandler@575] - ******* GOODBYE /10.10.34.11:52844 ******** +2015-07-29 19:21:16,835 - WARN [LearnerHandler-/10.10.34.13:57653:LearnerHandler@575] - ******* GOODBYE /10.10.34.13:57653 ******** +2015-07-29 19:21:26,625 - ERROR [LearnerHandler-/10.10.34.11:52855:LearnerHandler@562] - Unexpected exception causing shutdown while sock still open +2015-07-29 19:21:31,738 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:21:31,836 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:54788 +2015-07-29 19:21:35,084 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:21:35,284 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:42624 +2015-07-29 19:21:35,292 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:21:38,426 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:21:38,625 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:42634 +2015-07-29 19:21:38,626 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:21:41,969 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:21:41,976 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:21:41,976 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:21:45,107 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:21:45,109 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:21:45,200 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:54830 +2015-07-29 19:21:48,542 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:21:48,545 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:21:51,886 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:54857 +2015-07-29 19:21:51,887 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:21:52,000 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:21:58,680 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:22:01,826 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:22:05,161 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:22:05,251 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:22:08,591 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:22:08,701 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:22:08,703 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:42747 +2015-07-29 19:22:15,277 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:22:18,520 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:22:18,628 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:22:21,958 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:22:25,203 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:58282 +2015-07-29 19:22:25,295 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:22:28,748 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:42813 +2015-07-29 19:22:28,748 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:22:28,749 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:22:42,000 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:22:48,794 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:42885 +2015-07-29 19:22:55,364 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:22:55,483 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:42917 +2015-07-29 19:22:58,628 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:22:58,710 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:22:58,818 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:22:58,823 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:42926 +2015-07-29 19:22:58,824 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:23:01,969 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:23:01,977 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:23:05,500 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:23:08,841 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:23:12,078 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:23:12,182 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:23:15,435 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:23:18,864 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:23:22,092 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:23:25,440 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:23:25,546 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:23:28,902 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:23:32,242 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:23:38,924 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:23:42,263 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:23:45,608 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:23:48,744 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:23:48,819 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:23:48,945 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:23:52,080 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:23:52,094 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:23:52,166 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:55289 +2015-07-29 19:23:52,167 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:23:52,285 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:23:55,508 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:24:02,100 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:24:02,115 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:58635 +2015-07-29 19:24:05,462 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:58652 +2015-07-29 19:24:05,463 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:24:05,530 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:24:08,871 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:55346 +2015-07-29 19:24:08,884 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:24:12,123 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:24:12,331 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:24:12,334 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:24:19,011 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:24:22,234 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:24:25,680 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:43233 +2015-07-29 19:24:25,681 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:24:28,942 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:24:29,022 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:24:35,596 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:24:35,703 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:24:38,851 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:58764 +2015-07-29 19:24:42,397 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:24:45,532 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:58787 +2015-07-29 19:24:45,647 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:24:48,888 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:24:48,958 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:24:52,310 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:24:52,417 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:24:55,555 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:58823 +2015-07-29 19:24:55,570 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:24:55,669 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:24:58,991 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:24:59,099 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:43358 +2015-07-29 19:25:02,441 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:25:02,441 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:25:05,591 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:58865 +2015-07-29 19:25:05,661 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:55548 +2015-07-29 19:25:05,783 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:25:09,110 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:25:09,122 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:25:12,262 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:25:15,614 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:25:15,695 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:25:15,711 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:25:15,802 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:25:15,803 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:25:19,035 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:25:25,630 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:25:29,074 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:25:29,166 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:25:32,397 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:55648 +2015-07-29 19:25:32,505 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:25:39,079 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:25:39,080 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:25:39,188 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:25:42,340 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:25:49,016 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:25:49,027 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:25:57,870 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:43557 +2015-07-29 19:26:04,443 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:26:07,781 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:26:07,890 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:26:11,228 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:43606 +2015-07-29 19:26:14,363 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:26:14,459 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:26:17,799 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:55803 +2015-07-29 19:26:17,801 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:26:17,908 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:26:21,040 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:26:24,383 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:26:34,606 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:43693 +2015-07-29 19:26:44,416 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:26:44,418 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:26:44,625 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:43730 +2015-07-29 19:26:47,753 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:59250 +2015-07-29 19:26:51,197 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:55929 +2015-07-29 19:26:51,304 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:26:54,437 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:26:54,644 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:26:57,772 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:26:57,875 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:26:57,983 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:27:01,216 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:27:01,320 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:27:04,552 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:27:08,001 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:27:09,111 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:27:17,809 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:27:18,022 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:27:21,149 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:27:21,250 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:27:24,496 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:59416 +2015-07-29 19:27:24,498 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:27:27,836 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:27:27,838 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:27:27,927 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:27:27,928 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:56057 +2015-07-29 19:27:32,489 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:27:53,657 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:59489 +2015-07-29 19:27:53,761 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:56093 +2015-07-29 19:27:53,861 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:43921 +2015-07-29 19:28:00,339 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:59513 +2015-07-29 19:28:07,021 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:28:07,225 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:28:10,464 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:56154 +2015-07-29 19:28:10,465 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:28:13,703 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:28:17,044 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:28:17,144 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:56173 +2015-07-29 19:28:20,797 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:28:23,724 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:28:23,927 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:28:24,137 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:28:27,063 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:28:27,167 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:28:27,170 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:28:30,509 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:28:30,511 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:28:33,750 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:59657 +2015-07-29 19:28:33,951 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:28:40,426 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:28:40,431 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:59688 +2015-07-29 19:28:40,533 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:28:43,772 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:59703 +2015-07-29 19:28:43,772 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:28:43,871 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:56270 +2015-07-29 19:28:47,314 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:28:47,520 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:28:53,993 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:28:57,235 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:56322 +2015-07-29 19:28:57,235 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:28:57,236 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:29:00,478 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:59783 +2015-07-29 19:29:00,577 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:56339 +2015-07-29 19:29:03,812 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:29:03,816 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:29:04,018 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:29:04,027 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:29:10,495 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:29:10,701 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:29:17,176 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:59852 +2015-07-29 19:29:17,382 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:29:17,388 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:29:23,859 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:29:23,959 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:29:23,962 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:29:27,198 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:29:27,199 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:59897 +2015-07-29 19:29:27,298 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:56426 +2015-07-29 19:29:27,299 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:29:30,540 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:29:30,639 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:29:37,321 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:29:40,559 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:29:40,562 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:29:40,566 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:29:40,664 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:56483 +2015-07-29 19:29:43,899 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:59968 +2015-07-29 19:29:44,109 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:29:44,110 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:29:47,343 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:29:50,793 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:29:54,022 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:29:54,133 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:29:54,134 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:29:57,472 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:29:57,473 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:29:57,474 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:30:00,813 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:30:00,814 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:30:04,152 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:44387 +2015-07-29 19:30:04,154 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:30:07,289 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:30:10,625 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:60068 +2015-07-29 19:30:10,728 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:30:10,729 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:30:13,966 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:30:20,650 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:30:20,748 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:30:20,857 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:30:23,989 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:30:23,995 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:30:27,429 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:56644 +2015-07-29 19:30:34,221 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:30:37,451 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:30:37,451 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:30:40,692 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:30:47,372 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:30:47,582 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:30:50,712 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:60213 +2015-07-29 19:30:50,712 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:30:50,923 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:44558 +2015-07-29 19:30:54,053 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:30:54,151 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:30:57,394 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:30:57,395 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:30:57,492 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:31:00,739 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:31:00,945 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:31:07,510 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:56786 +2015-07-29 19:31:07,513 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:31:14,096 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:31:14,103 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:31:17,437 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:31:17,534 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:56830 +2015-07-29 19:31:20,785 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:31:20,871 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:56834 +2015-07-29 19:31:27,554 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:31:27,555 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:31:27,555 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:31:27,667 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:31:30,892 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:31:34,139 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:31:34,233 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:31:41,026 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:31:44,257 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:31:47,597 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:56935 +2015-07-29 19:31:50,937 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:31:51,046 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:31:51,049 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:31:54,184 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:31:54,276 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:56959 +2015-07-29 19:31:57,617 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:31:57,726 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:44795 +2015-07-29 19:32:00,861 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:32:07,543 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:32:07,546 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:32:11,086 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:44842 +2015-07-29 19:32:11,091 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:32:14,227 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:32:14,431 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:32:17,565 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:32:17,766 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:44866 +2015-07-29 19:32:17,777 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:32:20,906 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:32:21,111 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:44879 +2015-07-29 19:32:21,114 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:32:24,338 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:32:24,454 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:32:27,585 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:60575 +2015-07-29 19:32:27,586 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:32:27,586 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:32:27,588 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:32:31,017 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:32:31,018 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:32:34,356 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:32:37,607 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:32:40,947 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:32:40,948 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:32:41,038 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:32:41,149 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:32:41,155 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:32:44,493 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:32:44,498 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:32:50,969 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:32:50,970 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:32:51,174 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:44989 +2015-07-29 19:32:51,176 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:32:54,397 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:32:54,510 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:32:54,515 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:33:01,078 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:57197 +2015-07-29 19:33:01,198 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:33:07,757 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:33:08,980 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:33:11,011 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:33:11,012 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:33:11,219 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:33:14,438 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:33:14,554 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:33:21,031 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:33:21,034 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:33:21,121 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:33:21,122 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:33:24,375 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:33:31,054 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:33:31,146 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:33:31,146 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:57309 +2015-07-29 19:33:31,147 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:33:37,733 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:33:37,931 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:33:44,413 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:33:44,508 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:33:47,846 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:33:51,095 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:33:51,295 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:33:54,435 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:33:54,525 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:33:57,773 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:60936 +2015-07-29 19:33:57,774 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:34:01,116 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:34:04,656 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:34:07,797 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:34:07,889 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:34:07,996 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:34:11,226 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:57449 +2015-07-29 19:34:11,335 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:45275 +2015-07-29 19:34:14,680 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:45295 +2015-07-29 19:34:17,817 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:34:17,908 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:34:18,016 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:34:21,249 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:34:24,497 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:34:24,586 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:57495 +2015-07-29 19:34:24,697 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:34:24,698 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:34:24,699 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:34:27,838 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:34:27,928 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:34:28,035 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:45334 +2015-07-29 19:34:28,037 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:34:31,268 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:57523 +2015-07-29 19:34:31,382 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:34:34,517 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:32868 +2015-07-29 19:34:34,610 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:34:34,723 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:34:35,197 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:34:37,858 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:34:37,859 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:34:41,198 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:34:44,628 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:34:44,742 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:34:47,879 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:34:48,076 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:45406 +2015-07-29 19:34:54,565 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:34:54,649 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:34:54,649 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:35:01,238 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:32964 +2015-07-29 19:35:01,244 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:35:04,781 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:35:08,008 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:35:11,348 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:35:11,352 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:35:11,461 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:35:14,605 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:35:14,606 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:35:14,692 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:35:14,798 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:35:14,801 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:45509 +2015-07-29 19:35:14,802 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:35:17,946 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:35:18,136 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:35:24,626 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:35:24,818 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:35:24,822 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:35:28,049 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:35:28,160 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:35:28,162 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:35:31,307 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:35:31,389 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:35:34,731 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:35:34,735 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:35:34,839 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:35:34,842 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:35:41,328 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:35:41,411 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:35:41,523 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:35:44,864 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:35:48,007 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:33138 +2015-07-29 19:35:48,009 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:35:48,094 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:35:51,543 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:35:54,882 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:45651 +2015-07-29 19:35:54,885 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:36:01,368 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:33186 +2015-07-29 19:36:01,453 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:36:04,906 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:36:14,809 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:57889 +2015-07-29 19:36:18,070 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:33246 +2015-07-29 19:36:18,151 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:57904 +2015-07-29 19:36:18,262 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:36:18,265 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:45738 +2015-07-29 19:36:21,410 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:33257 +2015-07-29 19:36:21,414 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:36:21,492 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:36:21,606 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:36:24,752 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:36:24,834 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:36:28,091 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:36:28,176 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:36:28,284 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:45770 +2015-07-29 19:36:31,627 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:36:34,771 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:33305 +2015-07-29 19:36:34,853 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:57965 +2015-07-29 19:36:34,962 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:36:38,112 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:36:38,193 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:57977 +2015-07-29 19:36:38,307 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:36:44,987 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:36:48,327 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:36:51,671 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:36:51,671 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:36:54,812 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:36:55,011 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:36:58,153 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:36:58,154 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:36:58,342 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:36:58,343 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:37:01,494 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:37:05,025 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:37:08,362 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:37:11,703 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:45923 +2015-07-29 19:37:15,046 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:37:21,538 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:37:21,611 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:37:21,726 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:37:27,222 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@627] - Got user-level KeeperException when processing sessionid:0x34ed93485090001 type:create cxid:0x55b8bb0f zxid:0x100000010 txntype:-1 reqpath:n/a Error Path:/home/curi/.zookeeper Error:KeeperErrorCode = NodeExists for /home/curi/.zookeeper +2015-07-29 19:39:01,170 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-29 19:48:30,969 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.16:56610 +2015-07-29 19:52:16,002 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x14ed93111f20005 +2015-07-29 19:52:16,002 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x24ed93119420008 +2015-07-29 19:52:20,004 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x14ed93111f20000 +2015-07-29 19:52:20,581 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.11:50822 +2015-07-29 19:53:12,538 - WARN [SendWorker:3:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:54:05,544 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.13:37229; will be dropped if server is in r-o mode +2015-07-29 19:54:05,544 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.13:37229 +2015-07-29 19:56:54,754 - INFO [WorkerReceiver[myid=2]:FastLeaderElection@542] - Notification: 3 (n.leader), 0x10000006b (n.zxid), 0x2 (n.round), LOOKING (n.state), 3 (n.sid), 0x1 (n.peerEPoch), LEADING (my state) +2015-07-29 19:57:37,058 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.11:50926 +2015-07-29 20:15:01,897 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.11:51168 +2015-07-29 20:39:58,002 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x24ed9311942000c +2015-07-29 21:01:43,687 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.21:51245 +2015-07-29 21:01:50,768 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.25:53326; will be dropped if server is in r-o mode +2015-07-29 21:34:47,357 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.12:54610 +2015-07-29 21:34:48,001 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x14ed93111f20020, timeout of 10000ms exceeded +2015-07-29 21:34:48,003 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x24ed93119420021 +2015-07-29 21:36:24,001 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x24ed93119420033, timeout of 10000ms exceeded +2015-07-29 21:36:26,000 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x24ed9311942002a, timeout of 10000ms exceeded +2015-07-29 21:39:29,974 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.27:32782 +2015-07-29 21:41:34,002 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x14ed93111f2003f +2015-07-29 23:05:07,344 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.28:37304 which had sessionid 0x24ed9311942004f +2015-07-29 23:05:16,002 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x34ed9ac1c1e0021 +2015-07-29 23:05:18,000 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x34ed9ac1c1e002b, timeout of 10000ms exceeded +2015-07-29 23:43:04,001 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x14ed93111f20046 +2015-07-29 23:44:24,329 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x34ed9ac1c1e0030 +2015-07-29 23:44:25,464 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.35:38016 +2015-07-29 23:44:25,695 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x14ed93111f2004f +2015-07-29 23:49:40,337 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.11:53468 +2015-07-29 23:50:50,001 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x34ed9ac1c1e0033, timeout of 10000ms exceeded +2015-07-29 23:50:50,001 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x14ed93111f20050 +2015-07-29 23:52:07,913 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.12:54643; will be dropped if server is in r-o mode +2015-07-29 23:52:10,300 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.17:46387 +2015-07-30 13:34:19,139 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.11:48701 +2015-07-30 14:09:14,000 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x14ed93111f20068, timeout of 20000ms exceeded +2015-07-30 14:38:08,000 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x24ed93119420073 +2015-07-30 14:52:23,211 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.13:37335 which had sessionid 0x24ed93119420065 +2015-07-30 14:52:27,546 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.11:53520 which had sessionid 0x24ed9311942005f +2015-07-30 14:52:27,546 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-30 15:13:13,987 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x34ed9ac1c1e005e +2015-07-30 15:13:52,745 - INFO [CommitProcessor:2:ZooKeeperServer@595] - Established session 0x24ed9311942007e with negotiated timeout 10000 for client /10.10.34.12:54673 +2015-07-30 15:18:48,000 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x34ed9ac1c1e0065, timeout of 20000ms exceeded +2015-07-30 15:24:39,217 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.11:53857 which had sessionid 0x24ed93119420082 +2015-07-30 15:34:30,623 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-30 15:35:06,129 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.11:54078 +2015-07-30 15:35:06,939 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.18:40006 +2015-07-30 15:35:06,940 - INFO [CommitProcessor:2:ZooKeeperServer@595] - Established session 0x24ed9311942008c with negotiated timeout 10000 for client /10.10.34.18:40006 +2015-07-30 15:35:08,822 - INFO [CommitProcessor:2:ZooKeeperServer@595] - Established session 0x24ed93119420091 with negotiated timeout 10000 for client /10.10.34.40:47629 +2015-07-30 15:35:20,505 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.11:54134 +2015-07-30 15:37:52,338 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-30 15:38:12,001 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x24ed93119420094 +2015-07-30 15:41:43,385 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-30 16:00:22,001 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x34ed9ac1c1e0081 +2015-07-30 16:00:30,000 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x34ed9ac1c1e0080 +2015-07-30 16:11:39,406 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-30 16:11:46,001 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x34ed9ac1c1e007f, timeout of 10000ms exceeded +2015-07-30 16:11:48,001 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x24ed9311942008e, timeout of 10000ms exceeded +2015-07-30 16:11:48,004 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x34ed9ac1c1e007a +2015-07-30 16:11:48,004 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x34ed9ac1c1e0078 +2015-07-30 16:12:05,225 - INFO [CommitProcessor:2:ZooKeeperServer@595] - Established session 0x24ed931194200a4 with negotiated timeout 10000 for client /10.10.34.32:39275 +2015-07-30 16:12:05,640 - INFO [CommitProcessor:2:ZooKeeperServer@595] - Established session 0x24ed931194200a7 with negotiated timeout 10000 for client /10.10.34.36:45209 +2015-07-30 16:12:14,000 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x34ed9ac1c1e0085 +2015-07-30 16:18:18,839 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.21:51262 which had sessionid 0x24ed931194200a0 +2015-07-30 16:18:19,077 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-30 16:18:30,003 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x14ed93111f200a7 +2015-07-30 16:18:34,001 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x14ed93111f2009f, timeout of 10000ms exceeded +2015-07-30 16:18:34,003 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x34ed9ac1c1e0083 +2015-07-30 16:18:39,030 - INFO [CommitProcessor:2:ZooKeeperServer@595] - Established session 0x24ed931194200af with negotiated timeout 10000 for client /10.10.34.16:56646 +2015-07-30 16:18:40,188 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.30:60436; will be dropped if server is in r-o mode +2015-07-30 16:21:28,000 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x34ed9ac1c1e008f, timeout of 10000ms exceeded +2015-07-30 16:21:28,000 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x24ed931194200ad, timeout of 10000ms exceeded +2015-07-30 16:49:18,001 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x14ed93111f200d2, timeout of 10000ms exceeded +2015-07-30 16:49:18,001 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x34ed9ac1c1e00ae +2015-07-30 17:12:00,363 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.13:37600 +2015-07-30 17:33:11,443 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.11:58424; will be dropped if server is in r-o mode +2015-07-30 17:49:05,204 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.11:52866 +2015-07-30 17:49:45,653 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-30 17:57:44,121 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:33209 +2015-07-30 18:08:02,428 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-30 18:17:53,378 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-30 18:18:02,134 - INFO [CommitProcessor:2:ZooKeeperServer@595] - Established session 0x24ede63a01b000a with negotiated timeout 10000 for client /10.10.34.13:52286 +2015-07-30 18:18:19,328 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.20:49010 which had sessionid 0x24ede63a01b000e +2015-07-30 18:18:28,772 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.11:53422 +2015-07-30 19:19:12,775 - INFO [CommitProcessor:2:ZooKeeperServer@595] - Established session 0x24ede63a01b0027 with negotiated timeout 10000 for client /10.10.34.13:52301 +2015-07-30 19:19:56,251 - INFO [CommitProcessor:2:ZooKeeperServer@595] - Established session 0x24ede63a01b002a with negotiated timeout 20000 for client /10.10.34.11:54338 +2015-07-30 19:35:00,506 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.13:52310 +2015-07-30 19:35:08,093 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.11:54576 +2015-07-30 20:41:23,305 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-30 21:03:49,284 - INFO [CommitProcessor:2:ZooKeeperServer@595] - Established session 0x24ede63a01b006c with negotiated timeout 10000 for client /10.10.34.40:47637 +2015-07-30 23:46:27,304 - INFO [main:QuorumPeerMain@127] - Starting quorum peer +2015-07-30 23:46:31,590 - INFO [QuorumPeer[myid=2]/0:0:0:0:0:0:0:0:2181:FileTxnSnapLog@240] - Snapshotting: 0x300000dcd to /var/lib/zookeeper/version-2/snapshot.300000dcd +2015-07-31 00:02:57,176 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.35:59458 +2015-07-31 00:16:10,015 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.37:32918 which had sessionid 0x24edfaa8717000c +2015-07-31 00:16:20,000 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x34edfaa9c22000d, timeout of 10000ms exceeded +2015-07-31 00:16:22,002 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x24edfaa87170002, timeout of 10000ms exceeded +2015-07-31 00:17:49,993 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.12:54126; will be dropped if server is in r-o mode +2015-07-31 00:17:51,716 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.11:57796 +2015-07-31 00:17:52,857 - INFO [CommitProcessor:2:ZooKeeperServer@595] - Established session 0x24edfaa87170018 with negotiated timeout 10000 for client /10.10.34.21:42521 +2015-07-31 00:18:58,001 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x24edfaa87170010, timeout of 10000ms exceeded +2015-07-31 00:19:19,100 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.24:45152 which had sessionid 0x24edfaa8717001a +2015-07-31 00:19:30,005 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x14edfaa86f60019 +2015-07-31 00:19:37,087 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.12:54230 +2015-07-31 00:19:39,077 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.34:56149 +2015-07-31 11:01:06,002 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x34edfaa9c220022, timeout of 10000ms exceeded +2015-07-31 11:01:06,003 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x14edfaa86f6002d +2015-07-31 11:01:06,006 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x24edfaa8717002d +2015-07-31 11:01:08,000 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x14edfaa86f6002a, timeout of 10000ms exceeded +2015-07-31 11:01:41,894 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.13:45817 which had sessionid 0x24edfaa87170022 +2015-07-31 11:01:55,633 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.12:54235 +2015-07-31 11:07:35,024 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-31 11:07:42,356 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.12:54237 which had sessionid 0x24edfaa87170035 +2015-07-31 11:07:52,001 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x14edfaa86f60031, timeout of 10000ms exceeded +2015-07-31 11:09:02,382 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.30:55417; will be dropped if server is in r-o mode +2015-07-31 11:09:03,412 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.40:42622 +2015-07-31 12:57:00,872 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-31 12:57:10,007 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x34edfaa9c22003d +2015-07-31 12:57:10,007 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x14edfaa86f60047 +2015-07-31 15:31:15,575 - INFO [main:DatadirCleanupManager@79] - autopurge.purgeInterval set to 0 +2015-07-31 15:31:41,457 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:59599 +2015-07-31 15:36:21,074 - INFO [QuorumPeer[myid=2]/0:0:0:0:0:0:0:0:2181:FileTxnSnapLog@240] - Snapshotting: 0x50000062e to /var/lib/zookeeper/version-2/snapshot.50000062e +2015-07-31 15:36:24,570 - INFO [LearnerHandler-/10.10.34.13:59348:LearnerHandler@263] - Follower sid: 3 : info : org.apache.zookeeper.server.quorum.QuorumPeer$QuorumServer@33557fe4 +2015-07-31 19:02:04,304 - WARN [SendWorker:1:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-31 21:22:52,022 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.27:36125 which had sessionid 0x24ee30a54f5000e +2015-07-31 21:23:04,002 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x34ee30a5c53000a +2015-07-31 21:23:12,518 - INFO [CommitProcessor:2:ZooKeeperServer@595] - Established session 0x24ee30a54f5001c with negotiated timeout 10000 for client /10.10.34.32:45013 +2015-07-31 21:24:52,001 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x24ee30a54f50017, timeout of 10000ms exceeded +2015-07-31 21:24:54,002 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x24ee30a54f5001d, timeout of 10000ms exceeded +2015-07-31 21:24:54,005 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x24ee30a54f50019 +2015-07-31 21:24:54,005 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x24ee30a54f5001a +2015-07-31 21:25:02,006 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x34ee30a5c530011 +2015-07-31 21:32:06,109 - INFO [CommitProcessor:2:ZooKeeperServer@595] - Established session 0x24ee30a54f5001e with negotiated timeout 20000 for client /10.10.34.11:45101 +2015-07-31 21:32:06,121 - INFO [CommitProcessor:2:ZooKeeperServer@595] - Established session 0x24ee30a54f5001f with negotiated timeout 10000 for client /10.10.34.11:45102 +2015-07-31 21:32:18,940 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.25:44785 +2015-07-31 21:32:20,163 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.41:45882 +2015-07-31 21:44:42,001 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x24ee30a54f50025, timeout of 10000ms exceeded +2015-07-31 21:44:44,001 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x24ee30a54f50027, timeout of 10000ms exceeded +2015-07-31 21:44:44,002 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x14ee3e057ed002a, timeout of 10000ms exceeded +2015-07-31 21:44:46,001 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x34ee30a5c53002a, timeout of 10000ms exceeded +2015-08-07 07:27:35,422 - WARN [QuorumPeer[myid=2]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-10 17:52:46,935 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.20:44648; will be dropped if server is in r-o mode +2015-08-10 17:53:26,762 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.18:49139; will be dropped if server is in r-o mode +2015-08-10 18:12:35,690 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-08-10 18:12:47,212 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.11:50990 +2015-08-10 18:12:48,994 - INFO [CommitProcessor:2:ZooKeeperServer@595] - Established session 0x24f0557806a001e with negotiated timeout 10000 for client /10.10.34.11:51000 +2015-08-10 18:12:50,548 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.25:44819; will be dropped if server is in r-o mode +2015-08-10 18:23:56,257 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.15:49471; will be dropped if server is in r-o mode +2015-08-10 18:23:56,268 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:Learner@107] - Revalidating client: 0x24f0557806a001c +2015-08-10 18:25:25,206 - INFO [main:DatadirCleanupManager@79] - autopurge.purgeInterval set to 0 +2015-08-10 18:25:25,239 - INFO [main:QuorumPeer@944] - maxSessionTimeout set to -1 +2015-08-10 18:25:25,413 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:44925 +2015-08-10 18:25:25,673 - INFO [QuorumPeer[myid=2]/0:0:0:0:0:0:0:0:2181:QuorumPeer@738] - FOLLOWING +2015-08-10 18:25:27,950 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.11:51259; will be dropped if server is in r-o mode +2015-08-10 18:25:27,951 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.11:51260 +2015-08-10 18:25:27,964 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@832] - Client attempting to renew session 0x24f0557806a0020 at /10.10.34.17:55969 +2015-08-10 18:25:52,337 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-08-10 18:25:52,537 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.13:36187 which had sessionid 0x24f0557806a001b +2015-08-10 18:26:03,376 - INFO [CommitProcessor:2:ZooKeeperServer@595] - Established session 0x24f1724b8af0009 with negotiated timeout 10000 for client /10.10.34.21:44834 +2015-08-10 18:35:11,692 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.11:51562 +2015-08-18 16:09:18,789 - INFO [QuorumPeer[myid=2]/0:0:0:0:0:0:0:0:2181:Environment@100] - Server environment:java.class.path=/etc/zookeeper/conf:/usr/share/java/jline.jar:/usr/share/java/log4j-1.2.jar:/usr/share/java/xercesImpl.jar:/usr/share/java/xmlParserAPIs.jar:/usr/share/java/netty.jar:/usr/share/java/slf4j-api.jar:/usr/share/java/slf4j-log4j12.jar:/usr/share/java/zookeeper.jar +2015-08-18 16:09:18,900 - INFO [LearnerHandler-/10.10.34.11:49928:Leader@598] - Have quorum of supporters; starting up and setting last processed zxid: 0xb00000000 +2015-08-18 16:09:22,982 - INFO [WorkerReceiver[myid=2]:FastLeaderElection@542] - Notification: 2 (n.leader), 0xa0000009a (n.zxid), 0x1 (n.round), FOLLOWING (n.state), 1 (n.sid), 0xa (n.peerEPoch), LEADING (my state) +2015-08-18 16:09:30,004 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x14f1724a6e80011, timeout of 10000ms exceeded +2015-08-18 16:09:30,009 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x34f1724a35e000c +2015-08-18 16:09:30,013 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x14f1724a6e8000d +2015-08-20 13:12:40,288 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.12:36322 +2015-08-20 13:13:18,000 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x14f3fdae8ba0002, timeout of 10000ms exceeded +2015-08-20 13:13:20,001 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x14f3fdae8ba0001 +2015-08-20 17:12:28,002 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x24f3fdaf738000a, timeout of 10000ms exceeded +2015-08-20 17:12:29,085 - INFO [QuorumPeer[myid=2]/0:0:0:0:0:0:0:0:2181:FinalRequestProcessor@415] - shutdown of request processor complete +2015-08-20 17:12:45,757 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.12:36358 +2015-08-20 17:12:45,757 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@354] - Exception causing close of session 0x0 due to java.io.IOException: ZooKeeperServer not running +2015-08-20 17:13:23,515 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.12:36401 (no session established for client) +2015-08-20 17:13:51,524 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@354] - Exception causing close of session 0x0 due to java.io.IOException: ZooKeeperServer not running +2015-08-20 17:14:13,880 - WARN [LearnerHandler-/10.10.34.13:42241:Leader@576] - First is 0x0 +2015-08-20 17:14:14,195 - INFO [WorkerReceiver[myid=2]:FastLeaderElection@542] - Notification: 1 (n.leader), 0xb0000007b (n.zxid), 0x2 (n.round), LOOKING (n.state), 1 (n.sid), 0xb (n.peerEPoch), LEADING (my state) +2015-08-20 17:14:14,196 - INFO [WorkerReceiver[myid=2]:FastLeaderElection@542] - Notification: 1 (n.leader), 0xb0000007b (n.zxid), 0x2 (n.round), LOOKING (n.state), 1 (n.sid), 0xb (n.peerEPoch), LEADING (my state) +2015-08-20 17:14:24,000 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x14f3fdae8ba0017, timeout of 10000ms exceeded +2015-08-20 17:14:24,000 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x14f3fdae8ba000c, timeout of 10000ms exceeded +2015-08-20 17:14:24,000 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x24f3fdaf7380008, timeout of 10000ms exceeded +2015-08-20 17:23:54,127 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.19:60483 which had sessionid 0x24f4a631df90002 +2015-08-20 17:24:04,002 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x24f4a631df90002, timeout of 10000ms exceeded +2015-08-20 17:24:09,157 - INFO [CommitProcessor:2:ZooKeeperServer@595] - Established session 0x24f4a631df9000e with negotiated timeout 10000 for client /10.10.34.16:53681 +2015-08-20 17:24:10,005 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x34f4a63146b000f +2015-08-20 17:24:10,007 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x14f4a6318b80004 +2015-08-20 17:24:11,330 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.40:39952 +2015-08-20 17:24:11,333 - INFO [CommitProcessor:2:ZooKeeperServer@595] - Established session 0x24f4a631df90016 with negotiated timeout 10000 for client /10.10.34.40:39952 +2015-08-20 17:26:17,909 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-08-20 17:26:25,623 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.11:34266 which had sessionid 0x24f4a631df9000a +2015-08-20 17:26:25,718 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.12:36890 which had sessionid 0x24f4a631df9000b +2015-08-20 19:32:56,125 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.15:59330 which had sessionid 0x24f4a631df9001d +2015-08-20 19:33:16,003 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x14f4a6318b80019 +2015-08-21 15:55:09,796 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.21:53818 +2015-08-21 15:55:10,840 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.35:47894; will be dropped if server is in r-o mode +2015-08-24 10:21:44,000 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x34f4a63146b0048, timeout of 10000ms exceeded +2015-08-25 11:14:51,514 - INFO [main:DatadirCleanupManager@79] - autopurge.purgeInterval set to 0 +2015-08-25 11:14:51,662 - INFO [main:FileSnap@83] - Reading snapshot /var/lib/zookeeper/version-2/snapshot.b00000084 +2015-08-25 11:14:53,074 - INFO [LearnerHandler-/10.10.34.11:32976:LearnerHandler@395] - Sending DIFF +2015-08-25 11:15:04,735 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x24f4a631df90029, timeout of 10000ms exceeded +2015-08-25 11:15:04,743 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x34f4a63146b003c +2015-08-25 11:15:04,750 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x14f4a6318b8002f +2015-08-25 11:26:27,861 - INFO [QuorumPeer[myid=2]/0:0:0:0:0:0:0:0:2181:QuorumPeer@670] - LOOKING +2015-08-25 11:26:28,145 - INFO [QuorumPeer[myid=2]/0:0:0:0:0:0:0:0:2181:Learner@325] - Getting a snapshot from leader +2015-07-29 17:42:53,528 - WARN [WorkerSender[myid=3]:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-07-29 17:43:29,975 - INFO [WorkerReceiver[myid=3]:FastLeaderElection@542] - Notification: 3 (n.leader), 0x0 (n.zxid), 0x1 (n.round), LOOKING (n.state), 3 (n.sid), 0x0 (n.peerEPoch), LOOKING (my state) +2015-07-29 17:43:47,783 - INFO [WorkerReceiver[myid=3]:FastLeaderElection@542] - Notification: 3 (n.leader), 0x0 (n.zxid), 0x1 (n.round), LOOKING (n.state), 3 (n.sid), 0x0 (n.peerEPoch), LOOKING (my state) +2015-07-29 19:21:29,146 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:21:32,680 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:21:35,820 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:21:35,823 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:21:36,029 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:21:39,171 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:21:39,257 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:21:39,364 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:21:42,521 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:21:42,707 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:21:42,709 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:44219 +2015-07-29 19:21:42,713 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:21:45,845 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:21:45,851 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:46538 +2015-07-29 19:21:46,049 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:21:46,050 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:21:52,735 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:44256 +2015-07-29 19:21:56,074 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:22:02,551 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:46592 +2015-07-29 19:22:02,761 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:22:05,991 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:22:09,332 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:22:09,447 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:22:19,462 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:22:19,469 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:22:22,613 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:22:22,700 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:22:22,812 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:22:26,040 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:47103 +2015-07-29 19:22:26,151 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:44377 +2015-07-29 19:22:29,382 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:22:32,643 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:22:35,982 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:46722 +2015-07-29 19:22:39,307 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:22:39,515 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:22:42,737 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:47157 +2015-07-29 19:22:46,105 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:47180 +2015-07-29 19:22:52,672 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:22:52,691 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:22:52,882 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:22:56,220 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:22:59,374 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:23:02,712 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:23:02,812 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:23:06,057 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:23:06,133 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:23:09,379 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:23:09,396 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:46842 +2015-07-29 19:23:09,473 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:47258 +2015-07-29 19:23:09,475 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:23:12,806 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:23:12,817 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:23:19,515 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:47300 +2015-07-29 19:23:19,600 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:23:26,282 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:23:26,298 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:44590 +2015-07-29 19:23:29,442 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:46914 +2015-07-29 19:23:36,118 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:23:36,221 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:23:39,463 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:23:39,465 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:23:39,561 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:23:42,806 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:23:42,873 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:47373 +2015-07-29 19:23:42,884 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:23:42,999 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:23:46,140 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:23:46,225 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:23:49,667 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:23:52,904 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:23:56,349 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:23:59,517 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:24:02,927 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:24:02,942 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:24:06,289 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:24:06,382 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:44732 +2015-07-29 19:24:06,383 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:24:09,630 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:24:09,631 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:24:09,728 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:24:12,879 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:24:13,071 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:24:16,291 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:24:16,410 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:24:26,230 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:24:26,239 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:24:29,570 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:24:29,592 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:24:29,755 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:44813 +2015-07-29 19:24:32,994 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:24:36,245 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:47145 +2015-07-29 19:24:36,247 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:24:36,272 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:24:39,704 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:24:46,274 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:24:46,275 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:24:46,284 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:24:49,624 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:24:49,724 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:24:49,725 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:47623 +2015-07-29 19:24:49,810 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:24:49,811 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:24:53,035 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:24:53,066 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:47635 +2015-07-29 19:24:59,647 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:25:06,519 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:25:09,678 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:25:13,018 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:47287 +2015-07-29 19:25:13,080 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:25:13,195 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:25:16,540 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:44990 +2015-07-29 19:25:19,761 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:25:26,556 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:45020 +2015-07-29 19:25:26,557 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:25:29,812 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:47767 +2015-07-29 19:25:33,048 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:25:33,154 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:25:36,389 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:25:36,392 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:47367 +2015-07-29 19:25:36,464 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:25:36,494 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:25:36,572 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:45053 +2015-07-29 19:25:36,585 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:25:39,729 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:25:43,070 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:25:43,145 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:25:49,854 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:25:55,059 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:25:55,268 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:25:58,399 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:26:01,736 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:26:01,947 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:26:11,758 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:26:15,102 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:26:16,412 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:47512 +2015-07-29 19:26:18,433 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:47515 +2015-07-29 19:26:18,534 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:47931 +2015-07-29 19:26:21,780 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:26:21,874 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:26:21,877 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:26:25,214 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:47954 +2015-07-29 19:26:28,458 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:26:31,792 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:26:32,001 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:26:35,137 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:26:35,235 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:26:38,476 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:47613 +2015-07-29 19:26:38,572 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:26:38,683 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:26:41,914 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:26:45,151 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:26:48,591 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:26:48,698 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:45309 +2015-07-29 19:26:48,698 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:26:51,831 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:26:51,929 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:48047 +2015-07-29 19:26:51,929 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:48048 +2015-07-29 19:26:55,269 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:26:55,270 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:26:58,715 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:45343 +2015-07-29 19:27:05,187 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:27:05,289 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:27:05,399 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:27:11,866 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:27:11,867 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:27:11,966 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:27:12,075 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:45392 +2015-07-29 19:27:15,206 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:27:16,526 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:27:18,644 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:27:18,756 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:27:18,757 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:27:18,758 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:45424 +2015-07-29 19:27:21,885 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:27:21,894 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:27:21,894 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:27:21,983 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:27:25,235 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:27:25,322 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:27:25,328 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:27:25,433 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:45439 +2015-07-29 19:27:51,154 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:27:51,255 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:27:54,493 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:27:54,494 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:48218 +2015-07-29 19:27:57,837 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:48235 +2015-07-29 19:28:01,176 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:28:01,179 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:28:04,413 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:28:04,517 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:48257 +2015-07-29 19:28:04,616 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:28:04,619 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:45532 +2015-07-29 19:28:14,542 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:28:17,882 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:28:21,118 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:48000 +2015-07-29 19:28:28,003 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:28:31,140 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:28:34,481 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:28:34,893 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:28:37,820 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:48067 +2015-07-29 19:28:37,825 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:28:38,023 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:45644 +2015-07-29 19:28:41,162 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:28:41,368 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:28:48,049 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:28:51,189 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:28:51,288 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:48426 +2015-07-29 19:28:51,387 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:28:51,387 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:45695 +2015-07-29 19:28:54,529 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:28:57,868 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:28:57,969 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:29:01,308 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:48457 +2015-07-29 19:29:01,309 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:29:04,546 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:48189 +2015-07-29 19:29:04,757 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:45745 +2015-07-29 19:29:04,958 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:29:07,993 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:29:11,328 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:29:11,330 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:29:11,333 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:29:11,438 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:29:14,671 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:29:17,913 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:48254 +2015-07-29 19:29:18,117 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:29:18,121 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:29:21,660 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:29:24,591 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:29:24,695 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:29:27,931 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:29:28,037 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:29:31,480 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:29:31,480 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:29:38,052 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:29:38,163 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:29:38,164 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:29:41,298 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:29:41,395 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:29:44,636 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:48373 +2015-07-29 19:29:48,076 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:29:48,077 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:29:48,181 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:45894 +2015-07-29 19:29:51,315 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:48394 +2015-07-29 19:29:51,524 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:29:51,525 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:29:58,000 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:48420 +2015-07-29 19:30:01,437 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:30:01,438 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:30:01,439 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:30:04,777 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:30:11,459 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:30:14,700 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:48478 +2015-07-29 19:30:14,700 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:30:21,380 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:48502 +2015-07-29 19:30:21,482 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:48751 +2015-07-29 19:30:21,483 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:30:24,725 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:30:28,163 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:30:38,084 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:30:38,183 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:48811 +2015-07-29 19:30:38,295 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:46083 +2015-07-29 19:30:41,426 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:30:41,635 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:30:41,637 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:30:44,766 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:30:48,107 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:30:48,107 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:48602 +2015-07-29 19:30:48,310 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:46110 +2015-07-29 19:30:48,317 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:30:51,658 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:30:54,996 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:46143 +2015-07-29 19:30:54,997 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:31:01,467 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:31:01,564 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:31:04,808 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:31:05,011 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:46170 +2015-07-29 19:31:05,018 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:31:08,148 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:48672 +2015-07-29 19:31:08,148 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:31:11,488 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:31:15,039 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:31:18,265 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:31:21,509 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:31:21,718 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:31:28,190 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:31:31,530 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:31:31,627 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:31:34,969 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:31:38,413 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:31:41,554 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:31:41,759 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:31:45,098 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:31:48,439 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:31:51,572 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:31:51,573 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:31:51,669 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:49076 +2015-07-29 19:31:55,114 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:31:58,253 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:31:58,342 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:32:05,143 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:32:05,145 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:32:11,710 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:32:11,814 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:46410 +2015-07-29 19:32:15,050 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:32:18,505 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:32:24,976 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:32:25,174 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:46458 +2015-07-29 19:32:25,185 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:32:28,407 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:49206 +2015-07-29 19:32:28,409 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:32:31,747 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:49218 +2015-07-29 19:32:35,205 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:32:38,423 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:32:38,536 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:32:41,677 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:32:41,684 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:32:45,020 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:32:45,025 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:32:45,108 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:32:45,216 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:32:48,442 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:49270 +2015-07-29 19:32:51,698 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:32:51,906 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:46563 +2015-07-29 19:32:58,378 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:49095 +2015-07-29 19:32:58,464 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:32:58,471 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:49316 +2015-07-29 19:33:01,720 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:33:01,804 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:33:01,917 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:33:05,059 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:33:05,059 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:33:05,144 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:33:05,153 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:33:08,405 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:33:09,707 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:33:11,947 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:33:18,420 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:49183 +2015-07-29 19:33:21,850 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:33:21,966 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:33:25,100 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:33:25,102 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:49215 +2015-07-29 19:33:25,297 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:33:28,440 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:33:28,442 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:33:28,443 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:33:28,646 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:46694 +2015-07-29 19:33:31,786 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:33:31,872 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:33:35,217 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:33:38,666 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:33:41,895 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:33:45,140 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:49283 +2015-07-29 19:33:45,235 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:33:48,482 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:49300 +2015-07-29 19:33:51,917 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:33:51,917 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:33:55,162 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:33:55,163 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:33:55,368 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:33:58,503 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:34:02,048 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:34:05,182 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:49361 +2015-07-29 19:34:05,388 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:34:08,523 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:34:08,526 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:34:11,864 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:49396 +2015-07-29 19:34:15,209 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:34:15,295 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:34:18,635 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:49598 +2015-07-29 19:34:18,637 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:34:22,089 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:34:25,427 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:34:28,568 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:34:28,569 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:34:28,761 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:34:31,903 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:49480 +2015-07-29 19:34:31,906 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:34:31,913 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:34:32,107 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:46922 +2015-07-29 19:34:35,337 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:34:38,586 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:34:38,676 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:49670 +2015-07-29 19:34:38,787 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:34:41,927 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:34:41,929 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:34:41,936 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:34:42,129 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:34:45,265 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:34:48,617 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:34:48,696 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:34:48,697 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:34:48,808 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:34:51,949 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:34:51,956 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:49566 +2015-07-29 19:34:52,035 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:34:52,036 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:34:55,378 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:34:58,628 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:34:58,636 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:49590 +2015-07-29 19:34:58,716 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:35:01,969 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:35:02,057 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:35:02,168 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:47032 +2015-07-29 19:35:05,510 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:35:12,075 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:49786 +2015-07-29 19:35:12,078 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:35:12,186 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:35:15,420 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:35:18,677 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:49662 +2015-07-29 19:35:18,863 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:35:22,018 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:35:22,095 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:49822 +2015-07-29 19:35:25,543 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:35:25,550 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:47115 +2015-07-29 19:35:38,717 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:35:42,141 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:35:48,731 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:35:48,732 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:35:48,930 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:47199 +2015-07-29 19:35:52,078 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:35:52,160 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:35:58,950 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:47234 +2015-07-29 19:36:02,290 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:36:02,292 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:36:05,518 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:36:05,519 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:36:08,774 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:36:08,857 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:49993 +2015-07-29 19:36:08,858 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:36:12,304 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:36:12,311 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:47282 +2015-07-29 19:36:15,454 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:36:15,651 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:36:22,134 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:49880 +2015-07-29 19:36:22,333 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:36:28,819 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:36:29,010 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:47340 +2015-07-29 19:36:29,011 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:47342 +2015-07-29 19:36:32,240 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:36:35,499 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:49938 +2015-07-29 19:36:38,838 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:49949 +2015-07-29 19:36:42,177 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:49957 +2015-07-29 19:36:45,518 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:36:45,520 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:36:48,859 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:36:58,955 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:36:59,065 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:37:02,404 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:47454 +2015-07-29 19:37:02,415 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:47464 +2015-07-29 19:37:05,751 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:37:08,902 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:37:09,091 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:37:09,092 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:37:12,435 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:47500 +2015-07-29 19:37:18,925 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:37:19,003 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:53:54,912 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.13:54265 (no session established for client) +2015-07-29 19:54:00,915 - INFO [WorkerReceiver[myid=3]:FastLeaderElection@542] - Notification: 3 (n.leader), 0x10000006b (n.zxid), 0x2 (n.round), LOOKING (n.state), 3 (n.sid), 0x1 (n.peerEPoch), LOOKING (my state) +2015-07-29 19:55:01,647 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.13:54294 (no session established for client) +2015-07-29 19:55:02,980 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.13:54298 +2015-07-29 19:55:19,655 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.13:54310 +2015-07-29 21:01:45,071 - INFO [CommitProcessor:3:ZooKeeperServer@595] - Established session 0x34ed9ac1c1e0007 with negotiated timeout 10000 for client /10.10.34.12:59224 +2015-07-29 21:34:44,640 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.12:59230; will be dropped if server is in r-o mode +2015-07-29 21:34:46,432 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.12:59235 +2015-07-29 21:34:47,040 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.17:51260 +2015-07-29 23:02:33,103 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.38:43508 +2015-07-29 23:05:05,988 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-29 23:42:53,384 - INFO [CommitProcessor:3:ZooKeeperServer@595] - Established session 0x34ed9ac1c1e002e with negotiated timeout 10000 for client /10.10.34.42:39469 +2015-07-29 23:44:22,733 - INFO [CommitProcessor:3:ZooKeeperServer@595] - Established session 0x34ed9ac1c1e0036 with negotiated timeout 10000 for client /10.10.34.36:37583 +2015-07-29 23:44:23,034 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.39:45022 +2015-07-29 23:52:09,561 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.41:54923 +2015-07-30 14:38:37,500 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.11:35811 +2015-07-30 14:48:54,960 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-30 14:52:35,531 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.11:37021 +2015-07-30 15:13:40,916 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.12:59284 which had sessionid 0x34ed9ac1c1e0059 +2015-07-30 15:13:40,916 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-30 15:13:49,197 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.13:54387 +2015-07-30 15:13:54,423 - INFO [CommitProcessor:3:ZooKeeperServer@595] - Established session 0x34ed9ac1c1e0064 with negotiated timeout 10000 for client /10.10.34.11:37111 +2015-07-30 15:14:15,378 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.11:37116; will be dropped if server is in r-o mode +2015-07-30 15:32:23,858 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.11:37330 +2015-07-30 16:18:14,811 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.18:46783 which had sessionid 0x34ed9ac1c1e0086 +2015-07-30 16:18:36,028 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.11:40581 which had sessionid 0x34ed9ac1c1e0093 +2015-07-30 16:21:13,810 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-30 16:21:27,293 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.12:59323 +2015-07-30 16:34:25,605 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.13:54616; will be dropped if server is in r-o mode +2015-07-30 16:34:35,580 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.14:49822; will be dropped if server is in r-o mode +2015-07-30 16:36:05,149 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.11:41160 which had sessionid 0x34ed9ac1c1e00a9 +2015-07-30 17:11:56,508 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.12:59359 +2015-07-30 17:22:36,450 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.13:54649 +2015-07-30 17:34:50,730 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.11:41732 +2015-07-30 17:36:52,812 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-30 17:40:45,765 - WARN [RecvWorker:1:QuorumCnxManager$RecvWorker@762] - Connection broken for id 1, my id = 3, error = +2015-07-30 17:49:01,419 - INFO [CommitProcessor:3:ZooKeeperServer@595] - Established session 0x34ed9ac1c1e00d1 with negotiated timeout 10000 for client /10.10.34.11:49255 +2015-07-30 17:57:38,413 - INFO [QuorumPeer[myid=3]/0:0:0:0:0:0:0:0:2181:QuorumPeer@670] - LOOKING +2015-07-30 17:57:38,440 - INFO [WorkerReceiver[myid=3]:FastLeaderElection@542] - Notification: 3 (n.leader), 0x100001564 (n.zxid), 0x3 (n.round), FOLLOWING (n.state), 3 (n.sid), 0x2 (n.peerEPoch), FOLLOWING (my state) +2015-07-30 17:58:23,837 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.13:50180 +2015-07-30 19:19:12,507 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.11:50716; will be dropped if server is in r-o mode +2015-07-30 19:35:00,232 - INFO [CommitProcessor:3:ZooKeeperServer@595] - Established session 0x34ede65503f0025 with negotiated timeout 10000 for client /10.10.34.11:50961 +2015-07-30 19:35:00,326 - INFO [CommitProcessor:3:ZooKeeperServer@595] - Established session 0x34ede65503f0027 with negotiated timeout 10000 for client /10.10.34.12:56359 +2015-07-30 19:57:45,009 - INFO [CommitProcessor:3:ZooKeeperServer@595] - Established session 0x34ede65503f002d with negotiated timeout 20000 for client /10.10.34.11:51041 +2015-07-30 19:57:45,045 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.11:51043; will be dropped if server is in r-o mode +2015-07-30 19:59:02,357 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.11:51097 +2015-07-30 19:59:02,549 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.13:50224 +2015-07-30 20:06:22,905 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.11:51097 which had sessionid 0x34ede65503f002f +2015-07-30 20:06:22,989 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.12:56372 which had sessionid 0x34ede65503f0030 +2015-07-30 20:14:09,840 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.11:51393 +2015-07-30 20:36:32,026 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.12:56424; will be dropped if server is in r-o mode +2015-07-30 20:36:32,135 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.13:50253 +2015-07-30 21:01:49,990 - INFO [CommitProcessor:3:ZooKeeperServer@595] - Established session 0x34ede65503f0058 with negotiated timeout 20000 for client /10.10.34.11:51967 +2015-07-30 23:03:42,330 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-30 23:52:53,800 - INFO [main:QuorumPeer@933] - minSessionTimeout set to -1 +2015-07-30 23:52:57,092 - INFO [QuorumPeer[myid=3]/0:0:0:0:0:0:0:0:2181:Environment@100] - Server environment:os.name=Linux +2015-07-30 23:52:57,093 - INFO [QuorumPeer[myid=3]/0:0:0:0:0:0:0:0:2181:Environment@100] - Server environment:user.name=zookeeper +2015-07-31 00:02:53,198 - INFO [CommitProcessor:3:ZooKeeperServer@595] - Established session 0x34edfaa9c220002 with negotiated timeout 10000 for client /10.10.34.11:53000 +2015-07-31 00:02:56,431 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.24:37975 +2015-07-31 00:02:57,579 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.39:51758 +2015-07-31 00:15:23,611 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.11:53310 which had sessionid 0x34edfaa9c220012 +2015-07-31 00:16:12,152 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-31 00:17:54,495 - INFO [CommitProcessor:3:ZooKeeperServer@595] - Established session 0x34edfaa9c22001e with negotiated timeout 10000 for client /10.10.34.41:51908 +2015-07-31 11:07:41,903 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.13:42060 which had sessionid 0x34edfaa9c22002d +2015-07-31 11:09:00,683 - INFO [CommitProcessor:3:ZooKeeperServer@595] - Established session 0x34edfaa9c22003a with negotiated timeout 10000 for client /10.10.34.16:42267 +2015-07-31 11:09:02,264 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.34:55584; will be dropped if server is in r-o mode +2015-07-31 11:09:02,548 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.37:34701; will be dropped if server is in r-o mode +2015-07-31 15:15:17,186 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:53230 +2015-07-31 15:36:23,686 - INFO [main:QuorumPeer@933] - minSessionTimeout set to -1 +2015-07-31 15:36:23,865 - INFO [QuorumPeer[myid=3]/0:0:0:0:0:0:0:0:2181:Environment@100] - Server environment:java.home=/usr/lib/jvm/java-7-openjdk-amd64/jre +2015-07-31 15:36:23,884 - INFO [QuorumPeer[myid=3]/0:0:0:0:0:0:0:0:2181:Learner@325] - Getting a snapshot from leader +2015-07-31 21:24:18,366 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.11:59186 which had sessionid 0x34ee30a5c530018 +2015-07-31 21:32:18,447 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.23:51828 +2015-07-31 21:32:19,994 - INFO [CommitProcessor:3:ZooKeeperServer@595] - Established session 0x34ee30a5c53002b with negotiated timeout 10000 for client /10.10.34.42:37429 +2015-08-07 07:27:46,402 - INFO [WorkerReceiver[myid=3]:FastLeaderElection@542] - Notification: 3 (n.leader), 0x700000197 (n.zxid), 0x1 (n.round), LOOKING (n.state), 3 (n.sid), 0x7 (n.peerEPoch), LOOKING (my state) +2015-08-10 17:52:39,698 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.13:58180 +2015-08-10 17:53:14,914 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.12:33342 which had sessionid 0x34f0557885e0002 +2015-08-10 17:53:16,001 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x14f05578bd80006, timeout of 10000ms exceeded +2015-08-10 18:12:34,001 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x14f05578bd8000f, timeout of 10000ms exceeded +2015-08-10 18:12:34,004 - INFO [ProcessThread(sid:3 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x24f0557806a0010 \ No newline at end of file diff --git a/2026/day-19/backup.sh b/2026/day-19/backup.sh new file mode 100644 index 0000000000..3e71218c6a --- /dev/null +++ b/2026/day-19/backup.sh @@ -0,0 +1,54 @@ +#!/bin/bash + +# this is a script for backup with a 5 day rotation +# usage : ./backup.sh + +function display_usage { + echo "usage : ./backup.sh " +} + +# check arguments +if [ $# -ne 2 ]; then + display_usage + exit 1 +fi + +source_dir=$1 +backup_dir=$2 +timestamp=$(date '+%Y-%m-%d-%H-%M-%S') + +function create_backup { + + zip -r "${backup_dir}/backup_${timestamp}.zip" "${source_dir}" > /dev/null + + if [ $? -eq 0 ]; then + echo "Backup generated successfully for ${timestamp}" + else + echo "Backup failed" + exit 1 + fi +} + +function perform_rotation { + + max_backups=5 + + backups=($(ls -t "${backup_dir}"/backup_*.zip 2>/dev/null)) + + echo "Current backups:" + echo "${backups[@]}" + + if [ ${#backups[@]} -gt $max_backups ]; then + + backups_to_delete=("${backups[@]:$max_backups}") + + for backup in "${backups_to_delete[@]}" + do + rm -f "$backup" + echo "Deleted old backup: $backup" + done + fi +} + +create_backup +perform_rotation \ No newline at end of file diff --git a/2026/day-19/zookeper.log b/2026/day-19/zookeper.log new file mode 100644 index 0000000000..74c71dda07 --- /dev/null +++ b/2026/day-19/zookeper.log @@ -0,0 +1,2000 @@ +2015-07-29 17:41:44,747 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 3200 +2015-07-29 19:04:12,394 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:45307 +2015-07-29 19:04:29,071 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:04:29,079 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:13:17,524 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:13:24,282 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:13:24,370 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:57707 +2015-07-29 19:13:27,721 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:13:34,382 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:13:37,626 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:13:44,301 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:13:47,731 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:13:54,220 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:45382 +2015-07-29 19:13:54,399 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:14:04,406 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:14:07,559 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:14:07,653 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:14:24,329 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:14:37,585 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:14:44,256 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:45440 +2015-07-29 19:14:47,593 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:14:54,354 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:15:24,476 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:15:37,647 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:15:37,648 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:15:54,407 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:15:57,854 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:57895 +2015-07-29 19:16:04,412 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:16:04,414 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:16:07,659 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:16:14,520 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:16:24,348 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:16:27,865 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:16:27,865 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:16:34,433 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:16:44,440 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:47727 +2015-07-29 19:16:57,707 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:17:17,721 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:17:17,921 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:17:24,471 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:17:24,477 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:17:57,741 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:17:57,939 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:58035 +2015-07-29 19:17:57,955 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:18:04,430 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:18:07,748 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:18:07,756 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:18:14,511 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:47838 +2015-07-29 19:18:14,839 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:18:34,635 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:18:37,770 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:18:47,785 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:18:54,534 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:18:54,534 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:18:57,988 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:19:04,661 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:58116 +2015-07-29 19:21:36,502 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:45957 +2015-07-29 19:21:36,607 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:21:39,846 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:21:39,846 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:21:43,389 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:21:46,525 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:21:46,537 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:21:46,728 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:58303 +2015-07-29 19:21:49,960 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:48096 +2015-07-29 19:21:53,209 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:21:53,220 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:21:53,410 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:21:53,412 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:21:53,414 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:21:56,644 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:21:56,756 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:21:59,997 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:22:03,324 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:48141 +2015-07-29 19:22:03,337 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:22:03,439 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:22:10,020 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:22:13,256 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:22:13,257 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:22:16,799 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:22:20,143 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:58421 +2015-07-29 19:22:23,289 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:22:23,378 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:22:23,379 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:22:26,617 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:46128 +2015-07-29 19:22:26,618 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:22:26,634 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:22:26,734 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:22:26,829 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:22:26,830 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:58452 +2015-07-29 19:22:29,975 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:22:33,313 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:22:33,513 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:22:36,642 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:22:36,659 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:46173 +2015-07-29 19:22:36,659 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:22:40,083 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:48280 +2015-07-29 19:22:43,421 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:22:43,536 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:22:46,680 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:22:50,025 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:22:53,441 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:22:53,462 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:22:56,689 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:22:56,892 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:23:00,124 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:23:00,131 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:23:00,237 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:58565 +2015-07-29 19:23:03,387 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:23:03,464 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:23:03,590 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:23:06,729 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:23:13,491 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:23:13,596 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:23:16,755 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:23:16,848 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:48413 +2015-07-29 19:23:16,937 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:23:20,094 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:46329 +2015-07-29 19:23:20,095 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:23:20,173 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:23:20,278 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:23:23,518 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:23:26,760 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:23:26,979 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:23:30,110 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:46360 +2015-07-29 19:23:30,116 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:23:30,320 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:23:33,457 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:23:33,553 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:23:36,783 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:23:40,140 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:23:46,827 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:46424 +2015-07-29 19:23:46,830 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:23:46,917 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:23:50,171 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:23:53,488 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:46440 +2015-07-29 19:23:56,838 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:23:56,851 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:24:00,386 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:24:03,616 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:24:03,725 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:24:07,062 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:24:10,216 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:24:10,286 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:48600 +2015-07-29 19:24:13,542 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:24:13,553 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:46519 +2015-07-29 19:24:16,883 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:24:16,987 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:24:20,217 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:24:20,413 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:24:20,431 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:24:23,563 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:46552 +2015-07-29 19:24:23,574 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:24:23,578 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:24:30,451 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:24:36,927 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:24:37,012 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:24:40,383 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:24:43,814 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:24:50,301 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:24:50,374 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:24:57,160 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:24:57,175 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:25:03,663 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:25:03,744 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:25:03,857 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:59016 +2015-07-29 19:25:07,003 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:25:07,079 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:25:07,102 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:25:07,107 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:48811 +2015-07-29 19:25:10,536 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:59037 +2015-07-29 19:25:10,539 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:25:13,695 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:25:13,874 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:25:17,021 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:25:17,124 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:25:23,702 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:25:23,811 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:25:23,889 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:59078 +2015-07-29 19:25:27,058 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:25:27,242 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:25:30,398 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:46798 +2015-07-29 19:25:30,571 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:25:33,833 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:25:33,923 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:25:37,062 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:46812 +2015-07-29 19:25:37,065 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:25:37,257 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:59130 +2015-07-29 19:25:37,259 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:25:40,484 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:48922 +2015-07-29 19:25:40,600 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:25:43,751 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:25:47,102 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:25:47,195 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:25:50,507 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:25:50,537 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:25:50,615 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:27:55,066 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:47327 +2015-07-29 19:27:58,407 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:27:58,827 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:47351 +2015-07-29 19:28:02,167 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:47366 +2015-07-29 19:28:05,197 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:28:08,431 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:47390 +2015-07-29 19:28:08,636 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:59614 +2015-07-29 19:28:12,190 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:28:15,221 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:28:18,656 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:28:18,661 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:28:21,796 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:28:21,902 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:28:21,902 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:28:22,000 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:28:28,473 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:47472 +2015-07-29 19:28:31,823 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:28:32,018 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:59689 +2015-07-29 19:28:35,160 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:28:35,361 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:59706 +2015-07-29 19:28:38,703 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:59722 +2015-07-29 19:28:38,704 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:28:41,841 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:28:41,844 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:47540 +2015-07-29 19:28:42,254 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:28:48,527 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:47571 +2015-07-29 19:28:55,309 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:28:58,547 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:47615 +2015-07-29 19:29:01,988 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:49588 +2015-07-29 19:29:08,571 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:29:08,668 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:49610 +2015-07-29 19:29:08,669 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:29:08,670 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:29:08,671 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:29:12,009 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:29:12,115 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:29:12,115 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:29:12,116 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:29:15,349 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:29:15,349 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:29:15,353 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:29:18,798 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:29:21,933 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:29:22,033 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:29:22,136 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:29:22,340 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:29:25,274 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:29:28,612 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:29:28,820 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:29:29,020 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:29:32,056 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:29:35,500 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:59925 +2015-07-29 19:29:38,840 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:29:38,841 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:29:38,843 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:29:42,070 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:29:42,075 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:29:45,414 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:29:45,522 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:29:52,202 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:29:55,545 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:29:58,673 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:29:58,774 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:29:58,778 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:29:58,779 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:29:58,884 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:30:02,019 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:47885 +2015-07-29 19:30:02,117 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:49806 +2015-07-29 19:30:05,458 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:30:08,802 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:30:12,246 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:30:15,382 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:30:15,586 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:60070 +2015-07-29 19:30:18,723 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:30:22,162 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:30:25,405 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:30:25,608 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:30:25,608 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:30:25,609 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:30:35,630 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:30:38,760 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:30:38,863 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:49940 +2015-07-29 19:30:42,315 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:30:42,315 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:30:45,653 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:30:48,785 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:30:48,883 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:30:48,997 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:30:59,011 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:31:02,142 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:31:02,243 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:31:02,243 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:31:02,352 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:31:02,353 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:31:05,483 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:31:05,583 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:31:08,823 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:31:08,922 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:50043 +2015-07-29 19:31:15,504 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:31:32,214 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:31:32,214 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:31:32,420 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:31:35,546 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:31:35,760 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:31:39,093 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:31:39,095 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:60366 +2015-07-29 19:31:45,780 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:31:49,006 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:31:49,116 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:31:49,117 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:31:52,349 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:31:52,456 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:31:52,456 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:31:55,588 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:31:55,590 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:48289 +2015-07-29 19:31:55,592 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:31:55,793 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:60423 +2015-07-29 19:31:55,805 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:31:58,932 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:31:59,141 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:32:02,269 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:32:02,363 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:32:02,367 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:32:05,705 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:32:08,955 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:32:09,163 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:32:12,495 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:32:12,503 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:60489 +2015-07-29 19:32:15,845 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:32:18,976 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:32:22,405 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:32:22,525 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:32:25,653 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:32:25,748 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:32:29,085 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:50332 +2015-07-29 19:32:29,085 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:32:32,336 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:32:32,428 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:32:35,678 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:32:35,764 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:50354 +2015-07-29 19:32:39,216 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:32:42,355 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:32:42,357 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:32:42,443 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:32:42,557 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:32:49,036 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:32:49,042 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:48503 +2015-07-29 19:32:49,237 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:32:52,469 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:32:59,143 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:50434 +2015-07-29 19:33:02,398 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:33:02,398 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:48563 +2015-07-29 19:33:02,597 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:33:05,829 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:33:09,080 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:33:09,170 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:33:12,423 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:48609 +2015-07-29 19:33:12,618 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:33:12,627 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:33:13,727 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:48612 +2015-07-29 19:33:13,728 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:33:15,851 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:33:15,853 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:33:15,963 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:33:15,965 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:60717 +2015-07-29 19:33:19,190 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:33:19,298 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:33:19,303 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:60726 +2015-07-29 19:33:22,441 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:33:22,532 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:50526 +2015-07-29 19:33:23,749 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:33:25,872 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:33:25,873 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:33:25,983 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:60750 +2015-07-29 19:33:29,118 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:33:29,212 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:33:29,212 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:50546 +2015-07-29 19:33:29,326 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:33:32,459 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:33:32,552 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:33:35,800 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:33:35,894 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:33:39,140 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:33:39,344 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:33:42,574 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:33:42,575 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:50597 +2015-07-29 19:33:42,678 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:33:42,688 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:33:45,916 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:33:46,025 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:33:46,026 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:33:49,162 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:33:49,364 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:60834 +2015-07-29 19:33:52,594 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:33:52,595 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:50633 +2015-07-29 19:33:55,843 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:33:55,844 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:33:55,935 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:33:59,385 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:34:02,725 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:34:05,861 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:34:05,862 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:48814 +2015-07-29 19:34:05,863 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:34:05,863 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:48817 +2015-07-29 19:34:05,958 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:34:06,067 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:34:09,294 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:34:09,294 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:34:09,295 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:34:12,634 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:34:12,742 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:34:12,745 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:60918 +2015-07-29 19:34:12,747 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:34:15,884 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:34:15,884 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:34:16,089 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:34:26,102 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:34:29,246 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:34:29,447 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:34:29,448 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:60984 +2015-07-29 19:34:32,782 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:34:32,788 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:60996 +2015-07-29 19:34:39,358 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:34:42,809 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:34:46,038 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:34:46,038 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:34:49,487 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:34:52,717 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:50849 +2015-07-29 19:34:55,969 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:49023 +2015-07-29 19:35:02,651 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:35:02,846 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:35:05,992 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:35:06,078 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:35:09,326 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:35:09,526 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:32891 +2015-07-29 19:35:16,098 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:35:16,207 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:35:19,443 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:35:19,544 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:32924 +2015-07-29 19:35:22,888 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:35:29,368 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:35:29,372 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:35:29,458 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:35:36,142 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:35:42,928 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:33010 +2015-07-29 19:35:46,073 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:49204 +2015-07-29 19:35:49,417 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:35:49,417 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:35:49,498 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:51050 +2015-07-29 19:35:52,756 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:35:52,842 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:35:56,178 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:35:56,180 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:36:02,861 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:51104 +2015-07-29 19:36:06,119 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:36:09,456 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:36:09,645 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:36:16,136 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:36:16,221 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:36:16,331 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:36:16,334 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:36:19,480 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:36:22,816 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:36:22,901 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:36:22,902 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:36:26,155 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:36:26,156 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:36:26,157 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:36:26,349 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:33165 +2015-07-29 19:36:29,686 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:36:32,920 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:36:33,030 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:36:36,365 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:33198 +2015-07-29 19:36:36,370 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:36:39,516 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:36:39,597 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:36:42,859 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:36:42,939 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:36:43,049 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:33225 +2015-07-29 19:36:43,054 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:36:49,620 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:36:49,623 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:36:49,730 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:33250 +2015-07-29 19:36:49,735 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:33255 +2015-07-29 19:36:52,879 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:36:53,074 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:33266 +2015-07-29 19:36:56,220 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:36:56,302 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:51296 +2015-07-29 19:36:56,303 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:36:59,746 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:33282 +2015-07-29 19:37:02,901 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:37:09,774 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 1, error = +2015-07-29 19:37:12,919 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:37:12,920 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:49518 +2015-07-29 19:37:13,114 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:37:19,676 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:37:19,683 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:51380 +2015-07-29 19:52:04,792 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.18:42772 which had sessionid 0x14ed93111f20005 +2015-07-29 19:52:05,118 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-29 19:52:09,519 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.12:45542 which had sessionid 0x14ed93111f20002 +2015-07-29 19:54:13,615 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@832] - Client attempting to renew session 0x24ed93119420016 at /10.10.34.13:37115 +2015-07-29 19:54:45,337 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.13:37106 which had sessionid 0x14ed93111f20010 +2015-07-29 21:01:41,504 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.19:33425 +2015-07-29 21:34:45,452 - INFO [CommitProcessor:1:ZooKeeperServer@595] - Established session 0x14ed93111f20027 with negotiated timeout 10000 for client /10.10.34.13:37177 +2015-07-29 21:34:48,285 - INFO [CommitProcessor:1:ZooKeeperServer@595] - Established session 0x14ed93111f2002b with negotiated timeout 10000 for client /10.10.34.22:47073 +2015-07-29 21:39:24,986 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.13:37196 +2015-07-29 21:39:28,234 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.26:56952 +2015-07-29 23:44:21,576 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.11:49557 which had sessionid 0x14ed93111f20048 +2015-07-29 23:44:28,903 - ERROR [CommitProcessor:1:NIOServerCnxn@180] - Unexpected Exception: +2015-07-29 23:52:08,962 - INFO [CommitProcessor:1:ZooKeeperServer@595] - Established session 0x14ed93111f2005b with negotiated timeout 10000 for client /10.10.34.28:52117 +2015-07-29 23:52:09,163 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.30:38562 +2015-07-29 23:52:09,783 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.36:32876 +2015-07-29 23:52:09,785 - INFO [CommitProcessor:1:ZooKeeperServer@595] - Established session 0x14ed93111f2005f with negotiated timeout 10000 for client /10.10.34.36:32876 +2015-07-30 13:47:25,927 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.11:45997 +2015-07-30 14:42:40,474 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.11:49346 +2015-07-30 14:47:15,835 - INFO [CommitProcessor:1:ZooKeeperServer@595] - Established session 0x14ed93111f20079 with negotiated timeout 20000 for client /10.10.34.11:49800 +2015-07-30 14:52:21,906 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.29:39382 which had sessionid 0x14ed93111f2005d +2015-07-30 14:52:36,477 - INFO [CommitProcessor:1:ZooKeeperServer@595] - Established session 0x14ed93111f2007c with negotiated timeout 10000 for client /10.10.34.11:50276 +2015-07-30 14:53:21,340 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.11:50286 +2015-07-30 15:00:24,824 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.11:50301 +2015-07-30 15:00:24,825 - INFO [CommitProcessor:1:ZooKeeperServer@595] - Established session 0x14ed93111f20082 with negotiated timeout 10000 for client /10.10.34.11:50301 +2015-07-30 15:23:21,827 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.11:50402 +2015-07-30 15:35:04,462 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.20:56414 +2015-07-30 15:41:40,669 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.11:50940 which had sessionid 0x14ed93111f20099 +2015-07-30 16:09:17,019 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.11:52893 which had sessionid 0x14ed93111f2009b +2015-07-30 16:12:01,554 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.19:33442; will be dropped if server is in r-o mode +2015-07-30 16:12:02,180 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.29:39387 +2015-07-30 16:18:34,053 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.11:53821 +2015-07-30 16:18:34,149 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.12:45668 +2015-07-30 16:18:36,818 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.20:56418; will be dropped if server is in r-o mode +2015-07-30 16:18:38,680 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.42:34164; will be dropped if server is in r-o mode +2015-07-30 16:21:28,258 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.12:45675 +2015-07-30 16:34:50,091 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.11:54411; will be dropped if server is in r-o mode +2015-07-30 16:44:26,593 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.12:45682 which had sessionid 0x14ed93111f200cd +2015-07-30 16:44:36,930 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.13:37454; will be dropped if server is in r-o mode +2015-07-30 17:06:34,257 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.12:45697 which had sessionid 0x14ed93111f200d6 +2015-07-30 17:06:40,616 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.11:54632 +2015-07-30 17:06:40,816 - INFO [CommitProcessor:1:ZooKeeperServer@595] - Established session 0x14ed93111f200df with negotiated timeout 10000 for client /10.10.34.13:37467 +2015-07-30 17:11:54,937 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-30 17:13:32,714 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.11:54738 +2015-07-30 17:22:34,245 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-30 17:36:31,976 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.11:54983 which had sessionid 0x14ed93111f200f0 +2015-07-30 17:43:58,186 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:Environment@100] - Server environment:user.dir=/ +2015-07-30 17:49:05,943 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.12:45728; will be dropped if server is in r-o mode +2015-07-30 17:55:26,200 - WARN [WorkerSender[myid=1]:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-07-30 18:18:01,981 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.12:43125 +2015-07-30 18:18:02,003 - INFO [ProcessThread(sid:1 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x14ede63a5a70002 +2015-07-30 18:18:30,005 - INFO [ProcessThread(sid:1 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x34ede65503f0010 +2015-07-30 19:50:21,400 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-30 19:50:32,001 - INFO [ProcessThread(sid:1 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x14ede63a5a70023 +2015-07-30 19:59:02,538 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.13:38053; will be dropped if server is in r-o mode +2015-07-30 19:59:08,004 - INFO [ProcessThread(sid:1 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x34ede65503f002b +2015-07-30 20:06:34,001 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x24ede63a01b003b, timeout of 10000ms exceeded +2015-07-30 20:06:34,003 - INFO [ProcessThread(sid:1 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x24ede63a01b003b +2015-07-30 20:13:46,001 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x34ede65503f0036, timeout of 10000ms exceeded +2015-07-30 20:13:46,004 - INFO [ProcessThread(sid:1 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x34ede65503f0039 +2015-07-30 20:17:12,294 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-30 20:34:58,003 - INFO [ProcessThread(sid:1 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x14ede63a5a7003a +2015-07-30 20:35:02,324 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.13:38079; will be dropped if server is in r-o mode +2015-07-30 21:03:35,465 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-30 21:03:35,468 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.13:38088 which had sessionid 0x14ede63a5a70048 +2015-07-30 21:03:44,632 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.11:40489; will be dropped if server is in r-o mode +2015-07-30 21:03:44,634 - INFO [CommitProcessor:1:ZooKeeperServer@595] - Established session 0x14ede63a5a7004b with negotiated timeout 10000 for client /10.10.34.11:40489 +2015-07-30 21:03:47,578 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.21:37904 +2015-07-30 23:03:42,133 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.17:51214 which had sessionid 0x14ede63a5a70053 +2015-07-30 23:03:52,001 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x34ede65503f005c, timeout of 10000ms exceeded +2015-07-30 23:03:54,002 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x24ede63a01b0062, timeout of 10000ms exceeded +2015-07-30 23:43:22,414 - WARN [LearnerHandler-/10.10.34.12:35276:LearnerHandler@575] - ******* GOODBYE /10.10.34.12:35276 ******** +2015-07-30 23:43:23,613 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumPeer@670] - LOOKING +2015-07-30 23:44:01,784 - WARN [WorkerSender[myid=1]:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-07-30 23:44:04,784 - WARN [WorkerSender[myid=1]:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-07-30 23:44:58,183 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-07-30 23:49:40,005 - WARN [RecvWorker:3:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-30 23:52:26,272 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-07-31 00:02:57,202 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.40:40996; will be dropped if server is in r-o mode +2015-07-31 00:17:52,585 - INFO [CommitProcessor:1:ZooKeeperServer@595] - Established session 0x14edfaa86f60013 with negotiated timeout 10000 for client /10.10.34.27:44600 +2015-07-31 00:19:18,655 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-31 00:19:19,582 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-31 00:19:37,018 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.16:39498; will be dropped if server is in r-o mode +2015-07-31 11:01:40,975 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.13:54485 which had sessionid 0x14edfaa86f60021 +2015-07-31 11:01:54,714 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.12:34568 +2015-07-31 11:01:57,854 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.25:58975; will be dropped if server is in r-o mode +2015-07-31 11:09:01,762 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.33:39730; will be dropped if server is in r-o mode +2015-07-31 15:31:40,971 - INFO [Thread-1:QuorumCnxManager$Listener@486] - My election bind port: 0.0.0.0/0.0.0.0:3888 +2015-07-31 15:31:40,999 - INFO [WorkerSender[myid=1]:QuorumCnxManager@190] - Have smaller server identifier, so dropping the connection: (2, 1) +2015-07-31 15:31:42,213 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumPeer@738] - FOLLOWING +2015-07-31 15:33:29,640 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-07-31 19:30:07,398 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumPeer@670] - LOOKING +2015-07-31 19:30:07,403 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@740] - New election. My id = 1, proposed zxid=0x700000000 +2015-07-31 19:30:07,445 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:Environment@100] - Server environment:host.name=mesos-master-1 +2015-07-31 19:30:07,452 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:Follower@63] - FOLLOWING - LEADER ELECTION TOOK - 49 +2015-07-31 21:11:05,474 - INFO [CommitProcessor:1:ZooKeeperServer@595] - Established session 0x14ee3e057ed000c with negotiated timeout 10000 for client /10.10.34.37:49834 +2015-07-31 21:23:08,968 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.11:40061 +2015-07-31 21:23:08,969 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.11:40061 +2015-07-31 21:23:10,926 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.13:39525; will be dropped if server is in r-o mode +2015-07-31 21:23:12,897 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.35:48971; will be dropped if server is in r-o mode +2015-07-31 21:24:43,960 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-31 21:32:18,390 - INFO [CommitProcessor:1:ZooKeeperServer@595] - Established session 0x14ee3e057ed002c with negotiated timeout 10000 for client /10.10.34.19:43049 +2015-07-31 21:32:20,131 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.40:58713 +2015-07-31 21:44:41,270 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.12:59661 which had sessionid 0x14ee3e057ed0027 +2015-08-07 07:27:47,425 - INFO [WorkerReceiver[myid=1]:FastLeaderElection@542] - Notification: 3 (n.leader), 0x700000197 (n.zxid), 0x1 (n.round), LEADING (n.state), 3 (n.sid), 0x7 (n.peerEPoch), LOOKING (my state) +2015-08-07 07:27:47,650 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:Follower@63] - FOLLOWING - LEADER ELECTION TOOK - 238 +2015-08-10 17:52:39,654 - INFO [CommitProcessor:1:ZooKeeperServer@595] - Established session 0x14f05578bd80002 with negotiated timeout 10000 for client /10.10.34.12:46262 +2015-08-10 17:53:06,869 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-08-10 17:53:22,767 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.15:54175 +2015-08-10 17:53:22,870 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.16:40418; will be dropped if server is in r-o mode +2015-08-10 18:12:23,970 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.19:57338 which had sessionid 0x14f05578bd8000d +2015-08-10 18:12:24,076 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-08-10 18:12:24,375 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-08-10 18:13:25,200 - INFO [CommitProcessor:1:ZooKeeperServer@595] - Established session 0x14f05578bd80020 with negotiated timeout 10000 for client /10.10.34.11:38390 +2015-08-10 18:23:49,901 - INFO [main:DatadirCleanupManager@78] - autopurge.snapRetainCount set to 3 +2015-08-10 18:23:50,332 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:Environment@100] - Server environment:java.vendor=Oracle Corporation +2015-08-10 18:23:52,646 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:Learner@107] - Revalidating client: 0x14f05578bd80018 +2015-08-10 18:23:52,649 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:ZooKeeperServer@595] - Established session 0x14f05578bd80016 with negotiated timeout 10000 for client /10.10.34.13:38490 +2015-08-10 18:23:52,650 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:ZooKeeperServer@595] - Established session 0x14f05578bd80013 with negotiated timeout 10000 for client /10.10.34.11:38530 +2015-08-10 18:23:52,653 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@832] - Client attempting to renew session 0x14f05578bd8001b at /10.10.34.20:56374 +2015-08-10 18:25:22,080 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:Environment@100] - Server environment:zookeeper.version=3.4.5--1, built on 06/10/2013 17:26 GMT +2015-08-10 18:25:22,082 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:Environment@100] - Server environment:user.name=zookeeper +2015-08-10 18:25:24,332 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:Learner@107] - Revalidating client: 0x14f05578bd80013 +2015-08-10 18:25:39,907 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-08-10 18:27:49,007 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.12:46331 which had sessionid 0x14f1724a6e80004 +2015-08-18 16:09:13,285 - INFO [/10.10.34.11:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:34051 +2015-08-18 16:09:15,099 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:Environment@100] - Server environment:os.name=Linux +2015-08-20 13:28:51,889 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.11:54839 +2015-08-20 13:28:51,983 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.12:58349 +2015-08-20 17:12:29,467 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.11:56471 (no session established for client) +2015-08-20 17:14:11,414 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@354] - Exception causing close of session 0x0 due to java.io.IOException: ZooKeeperServer not running +2015-08-20 17:14:12,326 - INFO [WorkerReceiver[myid=1]:FastLeaderElection@542] - Notification: 2 (n.leader), 0xb00000084 (n.zxid), 0x2 (n.round), LOOKING (n.state), 1 (n.sid), 0xb (n.peerEPoch), LOOKING (my state) +2015-08-20 17:14:23,824 - INFO [WorkerReceiver[myid=1]:FastLeaderElection@542] - Notification: 3 (n.leader), 0xb0000007b (n.zxid), 0x2 (n.round), LOOKING (n.state), 3 (n.sid), 0xb (n.peerEPoch), FOLLOWING (my state) +2015-08-20 17:22:22,288 - INFO [CommitProcessor:1:ZooKeeperServer@595] - Established session 0x14f4a6318b80005 with negotiated timeout 10000 for client /10.10.34.11:56492 +2015-08-20 17:24:06,873 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.12:58913 +2015-08-20 17:24:07,582 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.18:36934 +2015-08-20 17:24:07,816 - INFO [CommitProcessor:1:ZooKeeperServer@595] - Established session 0x14f4a6318b80013 with negotiated timeout 10000 for client /10.10.34.20:43137 +2015-08-20 19:02:23,456 - INFO [CommitProcessor:1:ZooKeeperServer@595] - Established session 0x14f4a6318b80022 with negotiated timeout 10000 for client /10.10.34.30:43272 +2015-08-20 19:32:55,963 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.35:48997 which had sessionid 0x14f4a6318b80024 +2015-08-20 19:33:02,860 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-08-20 19:33:02,860 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.12:58917 which had sessionid 0x14f4a6318b80018 +2015-08-21 15:55:04,347 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.13:50545; will be dropped if server is in r-o mode +2015-08-21 15:55:07,600 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.30:43278 +2015-08-21 15:55:14,153 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.14:46136 +2015-08-24 15:26:54,494 - INFO [main:QuorumPeer@913] - tickTime set to 2000 +2015-08-24 15:27:03,681 - WARN [WorkerSender[myid=1]:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-24 15:29:13,641 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-24 15:36:13,663 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-24 15:37:13,664 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-24 15:51:13,708 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-24 15:55:13,717 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-24 15:57:13,723 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-24 16:02:13,739 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-24 16:03:13,740 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-24 16:11:13,765 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-24 16:12:13,767 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-24 16:37:13,837 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-24 16:51:13,876 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-24 17:29:13,977 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-24 17:39:14,002 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-24 18:02:14,063 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-24 18:04:14,068 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-24 18:28:14,133 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-24 18:31:14,142 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-24 18:41:14,170 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-24 18:47:14,187 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-24 18:51:14,196 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-24 19:01:14,221 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-24 19:05:14,230 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-24 19:09:14,240 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-24 19:19:14,265 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-24 19:31:14,292 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-24 19:45:14,327 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-24 19:55:14,351 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-24 20:01:14,364 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-24 20:16:14,399 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-24 20:56:14,493 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-24 20:57:14,495 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-24 21:07:14,519 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-24 21:11:14,529 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-24 21:26:14,562 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-24 22:04:14,650 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-24 22:08:14,659 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-24 22:09:14,662 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-24 22:10:14,663 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-24 22:16:14,677 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-24 22:17:14,678 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-24 22:25:14,698 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-24 22:32:14,713 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-24 22:39:14,728 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-24 22:42:14,733 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-24 22:45:14,741 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-24 22:48:14,746 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-24 22:49:14,750 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-24 22:57:14,766 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-24 23:04:14,782 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-24 23:09:14,792 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-24 23:25:14,825 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-24 23:26:14,827 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-24 23:38:14,850 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-24 23:58:14,891 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-25 00:00:14,897 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-25 00:14:14,924 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-25 00:23:14,943 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-25 00:26:14,949 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-25 00:28:14,953 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-25 00:42:14,982 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-25 00:44:14,985 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-25 01:12:15,044 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-25 01:45:15,113 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-25 01:47:15,116 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-25 02:06:15,155 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-25 02:09:15,162 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-25 02:36:15,217 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-25 02:54:15,254 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-25 02:56:15,258 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-25 03:16:15,297 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-25 03:28:15,323 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-25 03:29:15,325 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-25 03:30:15,327 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-25 03:33:15,333 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-25 03:38:15,343 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-25 03:54:15,375 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-25 04:10:15,407 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-25 04:14:15,416 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-25 04:21:15,429 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-25 04:28:15,443 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-25 05:00:15,508 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-25 05:08:15,525 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-25 05:09:15,527 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-25 05:46:15,601 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-25 05:50:15,608 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-25 05:58:15,624 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-25 05:58:15,626 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-25 06:41:15,711 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-25 06:58:15,745 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-25 07:03:15,756 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-25 07:04:15,757 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-25 07:04:15,758 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-25 07:16:15,781 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-25 07:27:15,803 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-25 08:20:15,909 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-25 08:21:15,911 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-25 08:23:15,916 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-25 08:28:15,925 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-25 08:29:15,928 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-25 08:33:15,936 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-25 08:49:15,968 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-25 09:09:16,008 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-25 09:11:16,012 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-25 09:16:16,022 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-25 09:19:16,027 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-25 09:24:16,037 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-08-25 10:13:16,137 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-25 10:14:16,139 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-25 10:42:16,195 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-25 10:50:16,211 - INFO [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@774] - Notification time out: 60000 +2015-08-25 11:03:16,237 - WARN [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-25 11:20:12,465 - WARN [RecvWorker:3:QuorumCnxManager$RecvWorker@762] - Connection broken for id 3, my id = 1, error = +2015-08-25 11:21:22,561 - WARN [WorkerSender[myid=1]:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-07-29 17:42:30,405 - INFO [QuorumPeer[myid=2]/0:0:0:0:0:0:0:0:2181:Environment@100] - Server environment:java.vendor=Oracle Corporation +2015-07-29 19:03:35,413 - ERROR [LearnerHandler-/10.10.34.11:52225:LearnerHandler@562] - Unexpected exception causing shutdown while sock still open +2015-07-29 19:03:54,584 - ERROR [LearnerHandler-/10.10.34.11:52241:LearnerHandler@562] - Unexpected exception causing shutdown while sock still open +2015-07-29 19:04:30,989 - WARN [LearnerHandler-/10.10.34.11:52264:LearnerHandler@575] - ******* GOODBYE /10.10.34.11:52264 ******** +2015-07-29 19:04:30,989 - ERROR [LearnerHandler-/10.10.34.11:52265:LearnerHandler@562] - Unexpected exception causing shutdown while sock still open +2015-07-29 19:04:40,999 - ERROR [LearnerHandler-/10.10.34.11:52273:LearnerHandler@562] - Unexpected exception causing shutdown while sock still open +2015-07-29 19:13:46,128 - WARN [LearnerHandler-/10.10.34.11:52308:LearnerHandler@575] - ******* GOODBYE /10.10.34.11:52308 ******** +2015-07-29 19:14:06,236 - WARN [LearnerHandler-/10.10.34.12:59060:LearnerHandler@575] - ******* GOODBYE /10.10.34.12:59060 ******** +2015-07-29 19:14:46,264 - WARN [LearnerHandler-/10.10.34.12:59103:LearnerHandler@575] - ******* GOODBYE /10.10.34.12:59103 ******** +2015-07-29 19:14:56,371 - WARN [LearnerHandler-/10.10.34.13:57247:LearnerHandler@575] - ******* GOODBYE /10.10.34.13:57247 ******** +2015-07-29 19:15:16,204 - ERROR [LearnerHandler-/10.10.34.11:52419:LearnerHandler@562] - Unexpected exception causing shutdown while sock still open +2015-07-29 19:15:56,423 - WARN [LearnerHandler-/10.10.34.13:57319:LearnerHandler@575] - ******* GOODBYE /10.10.34.13:57319 ******** +2015-07-29 19:16:06,243 - WARN [LearnerHandler-/10.10.34.11:52476:LearnerHandler@575] - ******* GOODBYE /10.10.34.11:52476 ******** +2015-07-29 19:16:06,336 - WARN [LearnerHandler-/10.10.34.12:59203:LearnerHandler@575] - ******* GOODBYE /10.10.34.12:59203 ******** +2015-07-29 19:16:16,339 - WARN [LearnerHandler-/10.10.34.12:59211:LearnerHandler@575] - ******* GOODBYE /10.10.34.12:59211 ******** +2015-07-29 19:16:26,268 - WARN [LearnerHandler-/10.10.34.11:52502:LearnerHandler@575] - ******* GOODBYE /10.10.34.11:52502 ******** +2015-07-29 19:16:26,447 - ERROR [LearnerHandler-/10.10.34.13:57354:LearnerHandler@562] - Unexpected exception causing shutdown while sock still open +2015-07-29 19:17:36,507 - ERROR [LearnerHandler-/10.10.34.13:57438:LearnerHandler@562] - Unexpected exception causing shutdown while sock still open +2015-07-29 19:17:56,522 - WARN [LearnerHandler-/10.10.34.13:57458:LearnerHandler@575] - ******* GOODBYE /10.10.34.13:57458 ******** +2015-07-29 19:18:26,565 - WARN [LearnerHandler-/10.10.34.13:57502:LearnerHandler@575] - ******* GOODBYE /10.10.34.13:57502 ******** +2015-07-29 19:18:56,377 - WARN [LearnerHandler-/10.10.34.11:52703:LearnerHandler@575] - ******* GOODBYE /10.10.34.11:52703 ******** +2015-07-29 19:18:56,457 - WARN [LearnerHandler-/10.10.34.12:59406:LearnerHandler@575] - ******* GOODBYE /10.10.34.12:59406 ******** +2015-07-29 19:20:16,690 - ERROR [LearnerHandler-/10.10.34.12:59455:LearnerHandler@562] - Unexpected exception causing shutdown while sock still open +2015-07-29 19:20:16,794 - WARN [LearnerHandler-/10.10.34.13:57580:LearnerHandler@575] - ******* GOODBYE /10.10.34.13:57580 ******** +2015-07-29 19:20:36,704 - ERROR [LearnerHandler-/10.10.34.12:59480:LearnerHandler@562] - Unexpected exception causing shutdown while sock still open +2015-07-29 19:20:46,814 - ERROR [LearnerHandler-/10.10.34.13:57617:LearnerHandler@562] - Unexpected exception causing shutdown while sock still open +2015-07-29 19:20:56,605 - ERROR [LearnerHandler-/10.10.34.11:52814:LearnerHandler@562] - Unexpected exception causing shutdown while sock still open +2015-07-29 19:20:56,608 - WARN [LearnerHandler-/10.10.34.11:52818:LearnerHandler@575] - ******* GOODBYE /10.10.34.11:52818 ******** +2015-07-29 19:21:16,619 - WARN [LearnerHandler-/10.10.34.11:52844:LearnerHandler@575] - ******* GOODBYE /10.10.34.11:52844 ******** +2015-07-29 19:21:16,835 - WARN [LearnerHandler-/10.10.34.13:57653:LearnerHandler@575] - ******* GOODBYE /10.10.34.13:57653 ******** +2015-07-29 19:21:26,625 - ERROR [LearnerHandler-/10.10.34.11:52855:LearnerHandler@562] - Unexpected exception causing shutdown while sock still open +2015-07-29 19:21:31,738 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:21:31,836 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:54788 +2015-07-29 19:21:35,084 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:21:35,284 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:42624 +2015-07-29 19:21:35,292 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:21:38,426 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:21:38,625 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:42634 +2015-07-29 19:21:38,626 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:21:41,969 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:21:41,976 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:21:41,976 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:21:45,107 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:21:45,109 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:21:45,200 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:54830 +2015-07-29 19:21:48,542 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:21:48,545 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:21:51,886 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:54857 +2015-07-29 19:21:51,887 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:21:52,000 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:21:58,680 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:22:01,826 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:22:05,161 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:22:05,251 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:22:08,591 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:22:08,701 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:22:08,703 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:42747 +2015-07-29 19:22:15,277 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:22:18,520 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:22:18,628 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:22:21,958 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:22:25,203 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:58282 +2015-07-29 19:22:25,295 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:22:28,748 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:42813 +2015-07-29 19:22:28,748 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:22:28,749 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:22:42,000 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:22:48,794 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:42885 +2015-07-29 19:22:55,364 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:22:55,483 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:42917 +2015-07-29 19:22:58,628 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:22:58,710 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:22:58,818 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:22:58,823 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:42926 +2015-07-29 19:22:58,824 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:23:01,969 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:23:01,977 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:23:05,500 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:23:08,841 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:23:12,078 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:23:12,182 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:23:15,435 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:23:18,864 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:23:22,092 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:23:25,440 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:23:25,546 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:23:28,902 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:23:32,242 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:23:38,924 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:23:42,263 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:23:45,608 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:23:48,744 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:23:48,819 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:23:48,945 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:23:52,080 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:23:52,094 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:23:52,166 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:55289 +2015-07-29 19:23:52,167 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:23:52,285 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:23:55,508 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:24:02,100 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:24:02,115 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:58635 +2015-07-29 19:24:05,462 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:58652 +2015-07-29 19:24:05,463 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:24:05,530 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:24:08,871 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:55346 +2015-07-29 19:24:08,884 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:24:12,123 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:24:12,331 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:24:12,334 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:24:19,011 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:24:22,234 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:24:25,680 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:43233 +2015-07-29 19:24:25,681 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:24:28,942 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:24:29,022 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:24:35,596 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:24:35,703 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:24:38,851 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:58764 +2015-07-29 19:24:42,397 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:24:45,532 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:58787 +2015-07-29 19:24:45,647 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:24:48,888 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:24:48,958 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:24:52,310 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:24:52,417 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:24:55,555 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:58823 +2015-07-29 19:24:55,570 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:24:55,669 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:24:58,991 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:24:59,099 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:43358 +2015-07-29 19:25:02,441 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:25:02,441 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:25:05,591 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:58865 +2015-07-29 19:25:05,661 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:55548 +2015-07-29 19:25:05,783 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:25:09,110 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:25:09,122 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:25:12,262 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:25:15,614 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:25:15,695 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:25:15,711 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:25:15,802 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:25:15,803 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:25:19,035 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:25:25,630 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:25:29,074 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:25:29,166 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:25:32,397 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:55648 +2015-07-29 19:25:32,505 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:25:39,079 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:25:39,080 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:25:39,188 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:25:42,340 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:25:49,016 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:25:49,027 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:25:57,870 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:43557 +2015-07-29 19:26:04,443 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:26:07,781 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:26:07,890 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:26:11,228 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:43606 +2015-07-29 19:26:14,363 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:26:14,459 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:26:17,799 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:55803 +2015-07-29 19:26:17,801 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:26:17,908 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:26:21,040 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:26:24,383 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:26:34,606 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:43693 +2015-07-29 19:26:44,416 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:26:44,418 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:26:44,625 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:43730 +2015-07-29 19:26:47,753 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:59250 +2015-07-29 19:26:51,197 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:55929 +2015-07-29 19:26:51,304 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:26:54,437 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:26:54,644 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:26:57,772 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:26:57,875 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:26:57,983 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:27:01,216 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:27:01,320 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:27:04,552 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:27:08,001 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:27:09,111 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:27:17,809 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:27:18,022 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:27:21,149 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:27:21,250 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:27:24,496 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:59416 +2015-07-29 19:27:24,498 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:27:27,836 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:27:27,838 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:27:27,927 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:27:27,928 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:56057 +2015-07-29 19:27:32,489 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:27:53,657 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:59489 +2015-07-29 19:27:53,761 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:56093 +2015-07-29 19:27:53,861 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:43921 +2015-07-29 19:28:00,339 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:59513 +2015-07-29 19:28:07,021 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:28:07,225 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:28:10,464 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:56154 +2015-07-29 19:28:10,465 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:28:13,703 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:28:17,044 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:28:17,144 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:56173 +2015-07-29 19:28:20,797 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:28:23,724 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:28:23,927 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:28:24,137 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:28:27,063 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:28:27,167 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:28:27,170 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:28:30,509 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:28:30,511 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:28:33,750 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:59657 +2015-07-29 19:28:33,951 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:28:40,426 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:28:40,431 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:59688 +2015-07-29 19:28:40,533 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:28:43,772 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:59703 +2015-07-29 19:28:43,772 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:28:43,871 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:56270 +2015-07-29 19:28:47,314 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:28:47,520 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:28:53,993 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:28:57,235 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:56322 +2015-07-29 19:28:57,235 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:28:57,236 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:29:00,478 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:59783 +2015-07-29 19:29:00,577 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:56339 +2015-07-29 19:29:03,812 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:29:03,816 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:29:04,018 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:29:04,027 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:29:10,495 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:29:10,701 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:29:17,176 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:59852 +2015-07-29 19:29:17,382 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:29:17,388 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:29:23,859 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:29:23,959 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:29:23,962 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:29:27,198 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:29:27,199 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:59897 +2015-07-29 19:29:27,298 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:56426 +2015-07-29 19:29:27,299 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:29:30,540 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:29:30,639 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:29:37,321 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:29:40,559 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:29:40,562 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:29:40,566 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:29:40,664 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:56483 +2015-07-29 19:29:43,899 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:59968 +2015-07-29 19:29:44,109 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:29:44,110 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:29:47,343 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:29:50,793 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:29:54,022 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:29:54,133 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:29:54,134 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:29:57,472 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:29:57,473 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:29:57,474 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:30:00,813 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:30:00,814 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:30:04,152 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:44387 +2015-07-29 19:30:04,154 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:30:07,289 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:30:10,625 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:60068 +2015-07-29 19:30:10,728 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:30:10,729 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:30:13,966 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:30:20,650 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:30:20,748 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:30:20,857 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:30:23,989 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:30:23,995 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:30:27,429 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:56644 +2015-07-29 19:30:34,221 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:30:37,451 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:30:37,451 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:30:40,692 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:30:47,372 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:30:47,582 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:30:50,712 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:60213 +2015-07-29 19:30:50,712 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:30:50,923 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:44558 +2015-07-29 19:30:54,053 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:30:54,151 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:30:57,394 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:30:57,395 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:30:57,492 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:31:00,739 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:31:00,945 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:31:07,510 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:56786 +2015-07-29 19:31:07,513 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:31:14,096 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:31:14,103 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:31:17,437 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:31:17,534 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:56830 +2015-07-29 19:31:20,785 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:31:20,871 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:56834 +2015-07-29 19:31:27,554 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:31:27,555 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:31:27,555 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:31:27,667 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:31:30,892 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:31:34,139 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:31:34,233 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:31:41,026 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:31:44,257 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:31:47,597 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:56935 +2015-07-29 19:31:50,937 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:31:51,046 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:31:51,049 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:31:54,184 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:31:54,276 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:56959 +2015-07-29 19:31:57,617 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:31:57,726 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:44795 +2015-07-29 19:32:00,861 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:32:07,543 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:32:07,546 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:32:11,086 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:44842 +2015-07-29 19:32:11,091 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:32:14,227 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:32:14,431 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:32:17,565 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:32:17,766 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:44866 +2015-07-29 19:32:17,777 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:32:20,906 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:32:21,111 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:44879 +2015-07-29 19:32:21,114 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:32:24,338 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:32:24,454 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:32:27,585 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:60575 +2015-07-29 19:32:27,586 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:32:27,586 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:32:27,588 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:32:31,017 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:32:31,018 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:32:34,356 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:32:37,607 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:32:40,947 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:32:40,948 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:32:41,038 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:32:41,149 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:32:41,155 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:32:44,493 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:32:44,498 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:32:50,969 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:32:50,970 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:32:51,174 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:44989 +2015-07-29 19:32:51,176 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:32:54,397 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:32:54,510 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:32:54,515 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:33:01,078 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:57197 +2015-07-29 19:33:01,198 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:33:07,757 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:33:08,980 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:33:11,011 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:33:11,012 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:33:11,219 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:33:14,438 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:33:14,554 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:33:21,031 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:33:21,034 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:33:21,121 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:33:21,122 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:33:24,375 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:33:31,054 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:33:31,146 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:33:31,146 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:57309 +2015-07-29 19:33:31,147 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:33:37,733 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:33:37,931 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:33:44,413 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:33:44,508 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:33:47,846 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:33:51,095 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:33:51,295 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:33:54,435 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:33:54,525 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:33:57,773 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:60936 +2015-07-29 19:33:57,774 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:34:01,116 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:34:04,656 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:34:07,797 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:34:07,889 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:34:07,996 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:34:11,226 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:57449 +2015-07-29 19:34:11,335 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:45275 +2015-07-29 19:34:14,680 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:45295 +2015-07-29 19:34:17,817 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:34:17,908 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:34:18,016 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:34:21,249 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:34:24,497 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:34:24,586 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:57495 +2015-07-29 19:34:24,697 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:34:24,698 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:34:24,699 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:34:27,838 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:34:27,928 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:34:28,035 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:45334 +2015-07-29 19:34:28,037 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:34:31,268 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:57523 +2015-07-29 19:34:31,382 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:34:34,517 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:32868 +2015-07-29 19:34:34,610 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:34:34,723 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:34:35,197 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:34:37,858 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:34:37,859 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:34:41,198 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:34:44,628 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:34:44,742 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:34:47,879 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:34:48,076 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:45406 +2015-07-29 19:34:54,565 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:34:54,649 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:34:54,649 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:35:01,238 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:32964 +2015-07-29 19:35:01,244 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:35:04,781 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:35:08,008 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:35:11,348 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:35:11,352 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:35:11,461 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:35:14,605 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:35:14,606 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:35:14,692 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:35:14,798 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:35:14,801 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:45509 +2015-07-29 19:35:14,802 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:35:17,946 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:35:18,136 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:35:24,626 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:35:24,818 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:35:24,822 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:35:28,049 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:35:28,160 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:35:28,162 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:35:31,307 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:35:31,389 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:35:34,731 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:35:34,735 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:35:34,839 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:35:34,842 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:35:41,328 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:35:41,411 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:35:41,523 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:35:44,864 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:35:48,007 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:33138 +2015-07-29 19:35:48,009 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:35:48,094 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:35:51,543 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:35:54,882 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:45651 +2015-07-29 19:35:54,885 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:36:01,368 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:33186 +2015-07-29 19:36:01,453 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:36:04,906 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:36:14,809 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:57889 +2015-07-29 19:36:18,070 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:33246 +2015-07-29 19:36:18,151 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:57904 +2015-07-29 19:36:18,262 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:36:18,265 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:45738 +2015-07-29 19:36:21,410 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:33257 +2015-07-29 19:36:21,414 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:36:21,492 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:36:21,606 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:36:24,752 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:36:24,834 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:36:28,091 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:36:28,176 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:36:28,284 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:45770 +2015-07-29 19:36:31,627 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:36:34,771 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:33305 +2015-07-29 19:36:34,853 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:57965 +2015-07-29 19:36:34,962 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:36:38,112 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:36:38,193 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:57977 +2015-07-29 19:36:38,307 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:36:44,987 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:36:48,327 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:36:51,671 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:36:51,671 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:36:54,812 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:36:55,011 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:36:58,153 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:36:58,154 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:36:58,342 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:36:58,343 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:37:01,494 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:37:05,025 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:37:08,362 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:37:11,703 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:45923 +2015-07-29 19:37:15,046 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:37:21,538 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:37:21,611 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:37:21,726 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 2, error = +2015-07-29 19:37:27,222 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@627] - Got user-level KeeperException when processing sessionid:0x34ed93485090001 type:create cxid:0x55b8bb0f zxid:0x100000010 txntype:-1 reqpath:n/a Error Path:/home/curi/.zookeeper Error:KeeperErrorCode = NodeExists for /home/curi/.zookeeper +2015-07-29 19:39:01,170 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-29 19:48:30,969 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.16:56610 +2015-07-29 19:52:16,002 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x14ed93111f20005 +2015-07-29 19:52:16,002 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x24ed93119420008 +2015-07-29 19:52:20,004 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x14ed93111f20000 +2015-07-29 19:52:20,581 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.11:50822 +2015-07-29 19:53:12,538 - WARN [SendWorker:3:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:54:05,544 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.13:37229; will be dropped if server is in r-o mode +2015-07-29 19:54:05,544 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.13:37229 +2015-07-29 19:56:54,754 - INFO [WorkerReceiver[myid=2]:FastLeaderElection@542] - Notification: 3 (n.leader), 0x10000006b (n.zxid), 0x2 (n.round), LOOKING (n.state), 3 (n.sid), 0x1 (n.peerEPoch), LEADING (my state) +2015-07-29 19:57:37,058 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.11:50926 +2015-07-29 20:15:01,897 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.11:51168 +2015-07-29 20:39:58,002 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x24ed9311942000c +2015-07-29 21:01:43,687 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.21:51245 +2015-07-29 21:01:50,768 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.25:53326; will be dropped if server is in r-o mode +2015-07-29 21:34:47,357 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.12:54610 +2015-07-29 21:34:48,001 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x14ed93111f20020, timeout of 10000ms exceeded +2015-07-29 21:34:48,003 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x24ed93119420021 +2015-07-29 21:36:24,001 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x24ed93119420033, timeout of 10000ms exceeded +2015-07-29 21:36:26,000 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x24ed9311942002a, timeout of 10000ms exceeded +2015-07-29 21:39:29,974 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.27:32782 +2015-07-29 21:41:34,002 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x14ed93111f2003f +2015-07-29 23:05:07,344 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.28:37304 which had sessionid 0x24ed9311942004f +2015-07-29 23:05:16,002 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x34ed9ac1c1e0021 +2015-07-29 23:05:18,000 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x34ed9ac1c1e002b, timeout of 10000ms exceeded +2015-07-29 23:43:04,001 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x14ed93111f20046 +2015-07-29 23:44:24,329 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x34ed9ac1c1e0030 +2015-07-29 23:44:25,464 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.35:38016 +2015-07-29 23:44:25,695 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x14ed93111f2004f +2015-07-29 23:49:40,337 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.11:53468 +2015-07-29 23:50:50,001 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x34ed9ac1c1e0033, timeout of 10000ms exceeded +2015-07-29 23:50:50,001 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x14ed93111f20050 +2015-07-29 23:52:07,913 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.12:54643; will be dropped if server is in r-o mode +2015-07-29 23:52:10,300 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.17:46387 +2015-07-30 13:34:19,139 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.11:48701 +2015-07-30 14:09:14,000 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x14ed93111f20068, timeout of 20000ms exceeded +2015-07-30 14:38:08,000 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x24ed93119420073 +2015-07-30 14:52:23,211 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.13:37335 which had sessionid 0x24ed93119420065 +2015-07-30 14:52:27,546 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.11:53520 which had sessionid 0x24ed9311942005f +2015-07-30 14:52:27,546 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-30 15:13:13,987 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x34ed9ac1c1e005e +2015-07-30 15:13:52,745 - INFO [CommitProcessor:2:ZooKeeperServer@595] - Established session 0x24ed9311942007e with negotiated timeout 10000 for client /10.10.34.12:54673 +2015-07-30 15:18:48,000 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x34ed9ac1c1e0065, timeout of 20000ms exceeded +2015-07-30 15:24:39,217 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.11:53857 which had sessionid 0x24ed93119420082 +2015-07-30 15:34:30,623 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-30 15:35:06,129 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.11:54078 +2015-07-30 15:35:06,939 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.18:40006 +2015-07-30 15:35:06,940 - INFO [CommitProcessor:2:ZooKeeperServer@595] - Established session 0x24ed9311942008c with negotiated timeout 10000 for client /10.10.34.18:40006 +2015-07-30 15:35:08,822 - INFO [CommitProcessor:2:ZooKeeperServer@595] - Established session 0x24ed93119420091 with negotiated timeout 10000 for client /10.10.34.40:47629 +2015-07-30 15:35:20,505 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.11:54134 +2015-07-30 15:37:52,338 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-30 15:38:12,001 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x24ed93119420094 +2015-07-30 15:41:43,385 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-30 16:00:22,001 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x34ed9ac1c1e0081 +2015-07-30 16:00:30,000 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x34ed9ac1c1e0080 +2015-07-30 16:11:39,406 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-30 16:11:46,001 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x34ed9ac1c1e007f, timeout of 10000ms exceeded +2015-07-30 16:11:48,001 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x24ed9311942008e, timeout of 10000ms exceeded +2015-07-30 16:11:48,004 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x34ed9ac1c1e007a +2015-07-30 16:11:48,004 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x34ed9ac1c1e0078 +2015-07-30 16:12:05,225 - INFO [CommitProcessor:2:ZooKeeperServer@595] - Established session 0x24ed931194200a4 with negotiated timeout 10000 for client /10.10.34.32:39275 +2015-07-30 16:12:05,640 - INFO [CommitProcessor:2:ZooKeeperServer@595] - Established session 0x24ed931194200a7 with negotiated timeout 10000 for client /10.10.34.36:45209 +2015-07-30 16:12:14,000 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x34ed9ac1c1e0085 +2015-07-30 16:18:18,839 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.21:51262 which had sessionid 0x24ed931194200a0 +2015-07-30 16:18:19,077 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-30 16:18:30,003 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x14ed93111f200a7 +2015-07-30 16:18:34,001 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x14ed93111f2009f, timeout of 10000ms exceeded +2015-07-30 16:18:34,003 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x34ed9ac1c1e0083 +2015-07-30 16:18:39,030 - INFO [CommitProcessor:2:ZooKeeperServer@595] - Established session 0x24ed931194200af with negotiated timeout 10000 for client /10.10.34.16:56646 +2015-07-30 16:18:40,188 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.30:60436; will be dropped if server is in r-o mode +2015-07-30 16:21:28,000 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x34ed9ac1c1e008f, timeout of 10000ms exceeded +2015-07-30 16:21:28,000 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x24ed931194200ad, timeout of 10000ms exceeded +2015-07-30 16:49:18,001 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x14ed93111f200d2, timeout of 10000ms exceeded +2015-07-30 16:49:18,001 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x34ed9ac1c1e00ae +2015-07-30 17:12:00,363 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.13:37600 +2015-07-30 17:33:11,443 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.11:58424; will be dropped if server is in r-o mode +2015-07-30 17:49:05,204 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.11:52866 +2015-07-30 17:49:45,653 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-30 17:57:44,121 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:33209 +2015-07-30 18:08:02,428 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-30 18:17:53,378 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-30 18:18:02,134 - INFO [CommitProcessor:2:ZooKeeperServer@595] - Established session 0x24ede63a01b000a with negotiated timeout 10000 for client /10.10.34.13:52286 +2015-07-30 18:18:19,328 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.20:49010 which had sessionid 0x24ede63a01b000e +2015-07-30 18:18:28,772 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.11:53422 +2015-07-30 19:19:12,775 - INFO [CommitProcessor:2:ZooKeeperServer@595] - Established session 0x24ede63a01b0027 with negotiated timeout 10000 for client /10.10.34.13:52301 +2015-07-30 19:19:56,251 - INFO [CommitProcessor:2:ZooKeeperServer@595] - Established session 0x24ede63a01b002a with negotiated timeout 20000 for client /10.10.34.11:54338 +2015-07-30 19:35:00,506 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.13:52310 +2015-07-30 19:35:08,093 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.11:54576 +2015-07-30 20:41:23,305 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-30 21:03:49,284 - INFO [CommitProcessor:2:ZooKeeperServer@595] - Established session 0x24ede63a01b006c with negotiated timeout 10000 for client /10.10.34.40:47637 +2015-07-30 23:46:27,304 - INFO [main:QuorumPeerMain@127] - Starting quorum peer +2015-07-30 23:46:31,590 - INFO [QuorumPeer[myid=2]/0:0:0:0:0:0:0:0:2181:FileTxnSnapLog@240] - Snapshotting: 0x300000dcd to /var/lib/zookeeper/version-2/snapshot.300000dcd +2015-07-31 00:02:57,176 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.35:59458 +2015-07-31 00:16:10,015 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.37:32918 which had sessionid 0x24edfaa8717000c +2015-07-31 00:16:20,000 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x34edfaa9c22000d, timeout of 10000ms exceeded +2015-07-31 00:16:22,002 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x24edfaa87170002, timeout of 10000ms exceeded +2015-07-31 00:17:49,993 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.12:54126; will be dropped if server is in r-o mode +2015-07-31 00:17:51,716 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.11:57796 +2015-07-31 00:17:52,857 - INFO [CommitProcessor:2:ZooKeeperServer@595] - Established session 0x24edfaa87170018 with negotiated timeout 10000 for client /10.10.34.21:42521 +2015-07-31 00:18:58,001 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x24edfaa87170010, timeout of 10000ms exceeded +2015-07-31 00:19:19,100 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.24:45152 which had sessionid 0x24edfaa8717001a +2015-07-31 00:19:30,005 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x14edfaa86f60019 +2015-07-31 00:19:37,087 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.12:54230 +2015-07-31 00:19:39,077 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.34:56149 +2015-07-31 11:01:06,002 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x34edfaa9c220022, timeout of 10000ms exceeded +2015-07-31 11:01:06,003 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x14edfaa86f6002d +2015-07-31 11:01:06,006 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x24edfaa8717002d +2015-07-31 11:01:08,000 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x14edfaa86f6002a, timeout of 10000ms exceeded +2015-07-31 11:01:41,894 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.13:45817 which had sessionid 0x24edfaa87170022 +2015-07-31 11:01:55,633 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.12:54235 +2015-07-31 11:07:35,024 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-31 11:07:42,356 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.12:54237 which had sessionid 0x24edfaa87170035 +2015-07-31 11:07:52,001 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x14edfaa86f60031, timeout of 10000ms exceeded +2015-07-31 11:09:02,382 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.30:55417; will be dropped if server is in r-o mode +2015-07-31 11:09:03,412 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.40:42622 +2015-07-31 12:57:00,872 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-31 12:57:10,007 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x34edfaa9c22003d +2015-07-31 12:57:10,007 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x14edfaa86f60047 +2015-07-31 15:31:15,575 - INFO [main:DatadirCleanupManager@79] - autopurge.purgeInterval set to 0 +2015-07-31 15:31:41,457 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:59599 +2015-07-31 15:36:21,074 - INFO [QuorumPeer[myid=2]/0:0:0:0:0:0:0:0:2181:FileTxnSnapLog@240] - Snapshotting: 0x50000062e to /var/lib/zookeeper/version-2/snapshot.50000062e +2015-07-31 15:36:24,570 - INFO [LearnerHandler-/10.10.34.13:59348:LearnerHandler@263] - Follower sid: 3 : info : org.apache.zookeeper.server.quorum.QuorumPeer$QuorumServer@33557fe4 +2015-07-31 19:02:04,304 - WARN [SendWorker:1:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-31 21:22:52,022 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.27:36125 which had sessionid 0x24ee30a54f5000e +2015-07-31 21:23:04,002 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x34ee30a5c53000a +2015-07-31 21:23:12,518 - INFO [CommitProcessor:2:ZooKeeperServer@595] - Established session 0x24ee30a54f5001c with negotiated timeout 10000 for client /10.10.34.32:45013 +2015-07-31 21:24:52,001 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x24ee30a54f50017, timeout of 10000ms exceeded +2015-07-31 21:24:54,002 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x24ee30a54f5001d, timeout of 10000ms exceeded +2015-07-31 21:24:54,005 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x24ee30a54f50019 +2015-07-31 21:24:54,005 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x24ee30a54f5001a +2015-07-31 21:25:02,006 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x34ee30a5c530011 +2015-07-31 21:32:06,109 - INFO [CommitProcessor:2:ZooKeeperServer@595] - Established session 0x24ee30a54f5001e with negotiated timeout 20000 for client /10.10.34.11:45101 +2015-07-31 21:32:06,121 - INFO [CommitProcessor:2:ZooKeeperServer@595] - Established session 0x24ee30a54f5001f with negotiated timeout 10000 for client /10.10.34.11:45102 +2015-07-31 21:32:18,940 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.25:44785 +2015-07-31 21:32:20,163 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.41:45882 +2015-07-31 21:44:42,001 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x24ee30a54f50025, timeout of 10000ms exceeded +2015-07-31 21:44:44,001 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x24ee30a54f50027, timeout of 10000ms exceeded +2015-07-31 21:44:44,002 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x14ee3e057ed002a, timeout of 10000ms exceeded +2015-07-31 21:44:46,001 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x34ee30a5c53002a, timeout of 10000ms exceeded +2015-08-07 07:27:35,422 - WARN [QuorumPeer[myid=2]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@368] - Cannot open channel to 3 at election address /10.10.34.13:3888 +2015-08-10 17:52:46,935 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.20:44648; will be dropped if server is in r-o mode +2015-08-10 17:53:26,762 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.18:49139; will be dropped if server is in r-o mode +2015-08-10 18:12:35,690 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-08-10 18:12:47,212 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.11:50990 +2015-08-10 18:12:48,994 - INFO [CommitProcessor:2:ZooKeeperServer@595] - Established session 0x24f0557806a001e with negotiated timeout 10000 for client /10.10.34.11:51000 +2015-08-10 18:12:50,548 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.25:44819; will be dropped if server is in r-o mode +2015-08-10 18:23:56,257 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.15:49471; will be dropped if server is in r-o mode +2015-08-10 18:23:56,268 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:Learner@107] - Revalidating client: 0x24f0557806a001c +2015-08-10 18:25:25,206 - INFO [main:DatadirCleanupManager@79] - autopurge.purgeInterval set to 0 +2015-08-10 18:25:25,239 - INFO [main:QuorumPeer@944] - maxSessionTimeout set to -1 +2015-08-10 18:25:25,413 - INFO [/10.10.34.12:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:44925 +2015-08-10 18:25:25,673 - INFO [QuorumPeer[myid=2]/0:0:0:0:0:0:0:0:2181:QuorumPeer@738] - FOLLOWING +2015-08-10 18:25:27,950 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.11:51259; will be dropped if server is in r-o mode +2015-08-10 18:25:27,951 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.11:51260 +2015-08-10 18:25:27,964 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@832] - Client attempting to renew session 0x24f0557806a0020 at /10.10.34.17:55969 +2015-08-10 18:25:52,337 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-08-10 18:25:52,537 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.13:36187 which had sessionid 0x24f0557806a001b +2015-08-10 18:26:03,376 - INFO [CommitProcessor:2:ZooKeeperServer@595] - Established session 0x24f1724b8af0009 with negotiated timeout 10000 for client /10.10.34.21:44834 +2015-08-10 18:35:11,692 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.11:51562 +2015-08-18 16:09:18,789 - INFO [QuorumPeer[myid=2]/0:0:0:0:0:0:0:0:2181:Environment@100] - Server environment:java.class.path=/etc/zookeeper/conf:/usr/share/java/jline.jar:/usr/share/java/log4j-1.2.jar:/usr/share/java/xercesImpl.jar:/usr/share/java/xmlParserAPIs.jar:/usr/share/java/netty.jar:/usr/share/java/slf4j-api.jar:/usr/share/java/slf4j-log4j12.jar:/usr/share/java/zookeeper.jar +2015-08-18 16:09:18,900 - INFO [LearnerHandler-/10.10.34.11:49928:Leader@598] - Have quorum of supporters; starting up and setting last processed zxid: 0xb00000000 +2015-08-18 16:09:22,982 - INFO [WorkerReceiver[myid=2]:FastLeaderElection@542] - Notification: 2 (n.leader), 0xa0000009a (n.zxid), 0x1 (n.round), FOLLOWING (n.state), 1 (n.sid), 0xa (n.peerEPoch), LEADING (my state) +2015-08-18 16:09:30,004 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x14f1724a6e80011, timeout of 10000ms exceeded +2015-08-18 16:09:30,009 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x34f1724a35e000c +2015-08-18 16:09:30,013 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x14f1724a6e8000d +2015-08-20 13:12:40,288 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.12:36322 +2015-08-20 13:13:18,000 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x14f3fdae8ba0002, timeout of 10000ms exceeded +2015-08-20 13:13:20,001 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x14f3fdae8ba0001 +2015-08-20 17:12:28,002 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x24f3fdaf738000a, timeout of 10000ms exceeded +2015-08-20 17:12:29,085 - INFO [QuorumPeer[myid=2]/0:0:0:0:0:0:0:0:2181:FinalRequestProcessor@415] - shutdown of request processor complete +2015-08-20 17:12:45,757 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.12:36358 +2015-08-20 17:12:45,757 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@354] - Exception causing close of session 0x0 due to java.io.IOException: ZooKeeperServer not running +2015-08-20 17:13:23,515 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.12:36401 (no session established for client) +2015-08-20 17:13:51,524 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@354] - Exception causing close of session 0x0 due to java.io.IOException: ZooKeeperServer not running +2015-08-20 17:14:13,880 - WARN [LearnerHandler-/10.10.34.13:42241:Leader@576] - First is 0x0 +2015-08-20 17:14:14,195 - INFO [WorkerReceiver[myid=2]:FastLeaderElection@542] - Notification: 1 (n.leader), 0xb0000007b (n.zxid), 0x2 (n.round), LOOKING (n.state), 1 (n.sid), 0xb (n.peerEPoch), LEADING (my state) +2015-08-20 17:14:14,196 - INFO [WorkerReceiver[myid=2]:FastLeaderElection@542] - Notification: 1 (n.leader), 0xb0000007b (n.zxid), 0x2 (n.round), LOOKING (n.state), 1 (n.sid), 0xb (n.peerEPoch), LEADING (my state) +2015-08-20 17:14:24,000 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x14f3fdae8ba0017, timeout of 10000ms exceeded +2015-08-20 17:14:24,000 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x14f3fdae8ba000c, timeout of 10000ms exceeded +2015-08-20 17:14:24,000 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x24f3fdaf7380008, timeout of 10000ms exceeded +2015-08-20 17:23:54,127 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.19:60483 which had sessionid 0x24f4a631df90002 +2015-08-20 17:24:04,002 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x24f4a631df90002, timeout of 10000ms exceeded +2015-08-20 17:24:09,157 - INFO [CommitProcessor:2:ZooKeeperServer@595] - Established session 0x24f4a631df9000e with negotiated timeout 10000 for client /10.10.34.16:53681 +2015-08-20 17:24:10,005 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x34f4a63146b000f +2015-08-20 17:24:10,007 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x14f4a6318b80004 +2015-08-20 17:24:11,330 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.40:39952 +2015-08-20 17:24:11,333 - INFO [CommitProcessor:2:ZooKeeperServer@595] - Established session 0x24f4a631df90016 with negotiated timeout 10000 for client /10.10.34.40:39952 +2015-08-20 17:26:17,909 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-08-20 17:26:25,623 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.11:34266 which had sessionid 0x24f4a631df9000a +2015-08-20 17:26:25,718 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.12:36890 which had sessionid 0x24f4a631df9000b +2015-08-20 19:32:56,125 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.15:59330 which had sessionid 0x24f4a631df9001d +2015-08-20 19:33:16,003 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x14f4a6318b80019 +2015-08-21 15:55:09,796 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.21:53818 +2015-08-21 15:55:10,840 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.35:47894; will be dropped if server is in r-o mode +2015-08-24 10:21:44,000 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x34f4a63146b0048, timeout of 10000ms exceeded +2015-08-25 11:14:51,514 - INFO [main:DatadirCleanupManager@79] - autopurge.purgeInterval set to 0 +2015-08-25 11:14:51,662 - INFO [main:FileSnap@83] - Reading snapshot /var/lib/zookeeper/version-2/snapshot.b00000084 +2015-08-25 11:14:53,074 - INFO [LearnerHandler-/10.10.34.11:32976:LearnerHandler@395] - Sending DIFF +2015-08-25 11:15:04,735 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x24f4a631df90029, timeout of 10000ms exceeded +2015-08-25 11:15:04,743 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x34f4a63146b003c +2015-08-25 11:15:04,750 - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x14f4a6318b8002f +2015-08-25 11:26:27,861 - INFO [QuorumPeer[myid=2]/0:0:0:0:0:0:0:0:2181:QuorumPeer@670] - LOOKING +2015-08-25 11:26:28,145 - INFO [QuorumPeer[myid=2]/0:0:0:0:0:0:0:0:2181:Learner@325] - Getting a snapshot from leader +2015-07-29 17:42:53,528 - WARN [WorkerSender[myid=3]:QuorumCnxManager@368] - Cannot open channel to 2 at election address /10.10.34.12:3888 +2015-07-29 17:43:29,975 - INFO [WorkerReceiver[myid=3]:FastLeaderElection@542] - Notification: 3 (n.leader), 0x0 (n.zxid), 0x1 (n.round), LOOKING (n.state), 3 (n.sid), 0x0 (n.peerEPoch), LOOKING (my state) +2015-07-29 17:43:47,783 - INFO [WorkerReceiver[myid=3]:FastLeaderElection@542] - Notification: 3 (n.leader), 0x0 (n.zxid), 0x1 (n.round), LOOKING (n.state), 3 (n.sid), 0x0 (n.peerEPoch), LOOKING (my state) +2015-07-29 19:21:29,146 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:21:32,680 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:21:35,820 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:21:35,823 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:21:36,029 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:21:39,171 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:21:39,257 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:21:39,364 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:21:42,521 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:21:42,707 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:21:42,709 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:44219 +2015-07-29 19:21:42,713 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:21:45,845 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:21:45,851 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:46538 +2015-07-29 19:21:46,049 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:21:46,050 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:21:52,735 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:44256 +2015-07-29 19:21:56,074 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:22:02,551 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:46592 +2015-07-29 19:22:02,761 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:22:05,991 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:22:09,332 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:22:09,447 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:22:19,462 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:22:19,469 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:22:22,613 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:22:22,700 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:22:22,812 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:22:26,040 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:47103 +2015-07-29 19:22:26,151 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:44377 +2015-07-29 19:22:29,382 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:22:32,643 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:22:35,982 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:46722 +2015-07-29 19:22:39,307 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:22:39,515 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:22:42,737 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:47157 +2015-07-29 19:22:46,105 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:47180 +2015-07-29 19:22:52,672 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:22:52,691 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:22:52,882 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:22:56,220 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:22:59,374 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:23:02,712 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:23:02,812 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:23:06,057 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:23:06,133 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:23:09,379 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:23:09,396 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:46842 +2015-07-29 19:23:09,473 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:47258 +2015-07-29 19:23:09,475 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:23:12,806 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:23:12,817 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:23:19,515 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:47300 +2015-07-29 19:23:19,600 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:23:26,282 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:23:26,298 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:44590 +2015-07-29 19:23:29,442 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:46914 +2015-07-29 19:23:36,118 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:23:36,221 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:23:39,463 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:23:39,465 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:23:39,561 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:23:42,806 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:23:42,873 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:47373 +2015-07-29 19:23:42,884 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:23:42,999 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:23:46,140 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:23:46,225 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:23:49,667 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:23:52,904 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:23:56,349 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:23:59,517 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:24:02,927 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:24:02,942 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:24:06,289 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:24:06,382 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:44732 +2015-07-29 19:24:06,383 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:24:09,630 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:24:09,631 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:24:09,728 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:24:12,879 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:24:13,071 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:24:16,291 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:24:16,410 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:24:26,230 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:24:26,239 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:24:29,570 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:24:29,592 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:24:29,755 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:44813 +2015-07-29 19:24:32,994 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:24:36,245 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:47145 +2015-07-29 19:24:36,247 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:24:36,272 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:24:39,704 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:24:46,274 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:24:46,275 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:24:46,284 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:24:49,624 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:24:49,724 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:24:49,725 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:47623 +2015-07-29 19:24:49,810 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:24:49,811 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:24:53,035 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:24:53,066 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:47635 +2015-07-29 19:24:59,647 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:25:06,519 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:25:09,678 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:25:13,018 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:47287 +2015-07-29 19:25:13,080 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:25:13,195 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:25:16,540 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:44990 +2015-07-29 19:25:19,761 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:25:26,556 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:45020 +2015-07-29 19:25:26,557 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:25:29,812 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:47767 +2015-07-29 19:25:33,048 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:25:33,154 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:25:36,389 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:25:36,392 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:47367 +2015-07-29 19:25:36,464 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:25:36,494 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:25:36,572 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:45053 +2015-07-29 19:25:36,585 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:25:39,729 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:25:43,070 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:25:43,145 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:25:49,854 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:25:55,059 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:25:55,268 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:25:58,399 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:26:01,736 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:26:01,947 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:26:11,758 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:26:15,102 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:26:16,412 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:47512 +2015-07-29 19:26:18,433 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:47515 +2015-07-29 19:26:18,534 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:47931 +2015-07-29 19:26:21,780 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:26:21,874 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:26:21,877 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:26:25,214 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:47954 +2015-07-29 19:26:28,458 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:26:31,792 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:26:32,001 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:26:35,137 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:26:35,235 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:26:38,476 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:47613 +2015-07-29 19:26:38,572 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:26:38,683 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:26:41,914 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:26:45,151 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:26:48,591 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:26:48,698 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:45309 +2015-07-29 19:26:48,698 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:26:51,831 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:26:51,929 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:48047 +2015-07-29 19:26:51,929 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:48048 +2015-07-29 19:26:55,269 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:26:55,270 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:26:58,715 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:45343 +2015-07-29 19:27:05,187 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:27:05,289 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:27:05,399 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:27:11,866 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:27:11,867 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:27:11,966 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:27:12,075 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:45392 +2015-07-29 19:27:15,206 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:27:16,526 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:27:18,644 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:27:18,756 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:27:18,757 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:27:18,758 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:45424 +2015-07-29 19:27:21,885 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:27:21,894 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:27:21,894 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:27:21,983 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:27:25,235 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:27:25,322 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:27:25,328 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:27:25,433 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:45439 +2015-07-29 19:27:51,154 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:27:51,255 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:27:54,493 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:27:54,494 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:48218 +2015-07-29 19:27:57,837 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:48235 +2015-07-29 19:28:01,176 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:28:01,179 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:28:04,413 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:28:04,517 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:48257 +2015-07-29 19:28:04,616 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:28:04,619 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:45532 +2015-07-29 19:28:14,542 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:28:17,882 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:28:21,118 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:48000 +2015-07-29 19:28:28,003 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:28:31,140 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:28:34,481 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:28:34,893 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:28:37,820 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:48067 +2015-07-29 19:28:37,825 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:28:38,023 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:45644 +2015-07-29 19:28:41,162 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:28:41,368 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:28:48,049 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:28:51,189 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:28:51,288 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:48426 +2015-07-29 19:28:51,387 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:28:51,387 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:45695 +2015-07-29 19:28:54,529 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:28:57,868 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:28:57,969 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:29:01,308 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:48457 +2015-07-29 19:29:01,309 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:29:04,546 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:48189 +2015-07-29 19:29:04,757 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:45745 +2015-07-29 19:29:04,958 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:29:07,993 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:29:11,328 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:29:11,330 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:29:11,333 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:29:11,438 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:29:14,671 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:29:17,913 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:48254 +2015-07-29 19:29:18,117 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:29:18,121 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:29:21,660 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:29:24,591 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:29:24,695 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:29:27,931 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:29:28,037 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:29:31,480 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:29:31,480 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:29:38,052 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:29:38,163 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:29:38,164 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:29:41,298 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:29:41,395 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:29:44,636 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:48373 +2015-07-29 19:29:48,076 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:29:48,077 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:29:48,181 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:45894 +2015-07-29 19:29:51,315 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:48394 +2015-07-29 19:29:51,524 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:29:51,525 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:29:58,000 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:48420 +2015-07-29 19:30:01,437 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:30:01,438 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:30:01,439 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:30:04,777 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:30:11,459 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:30:14,700 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:48478 +2015-07-29 19:30:14,700 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:30:21,380 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:48502 +2015-07-29 19:30:21,482 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:48751 +2015-07-29 19:30:21,483 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:30:24,725 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:30:28,163 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:30:38,084 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:30:38,183 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:48811 +2015-07-29 19:30:38,295 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:46083 +2015-07-29 19:30:41,426 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:30:41,635 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:30:41,637 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:30:44,766 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:30:48,107 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:30:48,107 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:48602 +2015-07-29 19:30:48,310 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:46110 +2015-07-29 19:30:48,317 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:30:51,658 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:30:54,996 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:46143 +2015-07-29 19:30:54,997 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:31:01,467 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:31:01,564 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:31:04,808 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:31:05,011 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:46170 +2015-07-29 19:31:05,018 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:31:08,148 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:48672 +2015-07-29 19:31:08,148 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:31:11,488 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:31:15,039 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:31:18,265 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:31:21,509 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:31:21,718 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:31:28,190 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:31:31,530 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:31:31,627 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:31:34,969 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:31:38,413 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:31:41,554 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:31:41,759 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:31:45,098 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:31:48,439 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:31:51,572 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:31:51,573 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:31:51,669 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:49076 +2015-07-29 19:31:55,114 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:31:58,253 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:31:58,342 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:32:05,143 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:32:05,145 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:32:11,710 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:32:11,814 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:46410 +2015-07-29 19:32:15,050 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:32:18,505 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:32:24,976 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:32:25,174 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:46458 +2015-07-29 19:32:25,185 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:32:28,407 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:49206 +2015-07-29 19:32:28,409 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:32:31,747 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:49218 +2015-07-29 19:32:35,205 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:32:38,423 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:32:38,536 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:32:41,677 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:32:41,684 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:32:45,020 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:32:45,025 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:32:45,108 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:32:45,216 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:32:48,442 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:49270 +2015-07-29 19:32:51,698 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:32:51,906 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:46563 +2015-07-29 19:32:58,378 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:49095 +2015-07-29 19:32:58,464 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:32:58,471 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:49316 +2015-07-29 19:33:01,720 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:33:01,804 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:33:01,917 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:33:05,059 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:33:05,059 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:33:05,144 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:33:05,153 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:33:08,405 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:33:09,707 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:33:11,947 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:33:18,420 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:49183 +2015-07-29 19:33:21,850 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:33:21,966 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:33:25,100 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:33:25,102 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:49215 +2015-07-29 19:33:25,297 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:33:28,440 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:33:28,442 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:33:28,443 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:33:28,646 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:46694 +2015-07-29 19:33:31,786 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:33:31,872 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:33:35,217 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:33:38,666 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:33:41,895 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:33:45,140 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:49283 +2015-07-29 19:33:45,235 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:33:48,482 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:49300 +2015-07-29 19:33:51,917 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:33:51,917 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:33:55,162 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:33:55,163 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:33:55,368 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:33:58,503 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:34:02,048 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:34:05,182 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:49361 +2015-07-29 19:34:05,388 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:34:08,523 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:34:08,526 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:34:11,864 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:49396 +2015-07-29 19:34:15,209 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:34:15,295 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:34:18,635 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:49598 +2015-07-29 19:34:18,637 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:34:22,089 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:34:25,427 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:34:28,568 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:34:28,569 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:34:28,761 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:34:31,903 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:49480 +2015-07-29 19:34:31,906 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:34:31,913 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:34:32,107 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:46922 +2015-07-29 19:34:35,337 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:34:38,586 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:34:38,676 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:49670 +2015-07-29 19:34:38,787 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:34:41,927 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:34:41,929 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:34:41,936 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:34:42,129 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:34:45,265 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:34:48,617 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:34:48,696 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:34:48,697 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:34:48,808 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:34:51,949 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:34:51,956 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:49566 +2015-07-29 19:34:52,035 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:34:52,036 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:34:55,378 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:34:58,628 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:34:58,636 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:49590 +2015-07-29 19:34:58,716 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:35:01,969 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:35:02,057 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:35:02,168 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:47032 +2015-07-29 19:35:05,510 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:35:12,075 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:49786 +2015-07-29 19:35:12,078 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:35:12,186 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:35:15,420 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:35:18,677 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:49662 +2015-07-29 19:35:18,863 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:35:22,018 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:35:22,095 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:49822 +2015-07-29 19:35:25,543 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:35:25,550 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:47115 +2015-07-29 19:35:38,717 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:35:42,141 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:35:48,731 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:35:48,732 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:35:48,930 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:47199 +2015-07-29 19:35:52,078 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:35:52,160 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:35:58,950 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:47234 +2015-07-29 19:36:02,290 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:36:02,292 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:36:05,518 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:36:05,519 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:36:08,774 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:36:08,857 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.12:49993 +2015-07-29 19:36:08,858 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:36:12,304 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:36:12,311 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:47282 +2015-07-29 19:36:15,454 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:36:15,651 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:36:22,134 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:49880 +2015-07-29 19:36:22,333 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:36:28,819 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:36:29,010 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:47340 +2015-07-29 19:36:29,011 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:47342 +2015-07-29 19:36:32,240 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:36:35,499 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:49938 +2015-07-29 19:36:38,838 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:49949 +2015-07-29 19:36:42,177 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:49957 +2015-07-29 19:36:45,518 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:36:45,520 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:36:48,859 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:36:58,955 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:36:59,065 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:37:02,404 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:47454 +2015-07-29 19:37:02,415 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:47464 +2015-07-29 19:37:05,751 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:37:08,902 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@688] - Send worker leaving thread +2015-07-29 19:37:09,091 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:37:09,092 - WARN [SendWorker:188978561024:QuorumCnxManager$SendWorker@679] - Interrupted while waiting for message on queue +2015-07-29 19:37:12,435 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.13:47500 +2015-07-29 19:37:18,925 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@762] - Connection broken for id 188978561024, my id = 3, error = +2015-07-29 19:37:19,003 - WARN [RecvWorker:188978561024:QuorumCnxManager$RecvWorker@765] - Interrupting SendWorker +2015-07-29 19:53:54,912 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.13:54265 (no session established for client) +2015-07-29 19:54:00,915 - INFO [WorkerReceiver[myid=3]:FastLeaderElection@542] - Notification: 3 (n.leader), 0x10000006b (n.zxid), 0x2 (n.round), LOOKING (n.state), 3 (n.sid), 0x1 (n.peerEPoch), LOOKING (my state) +2015-07-29 19:55:01,647 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.13:54294 (no session established for client) +2015-07-29 19:55:02,980 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.13:54298 +2015-07-29 19:55:19,655 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.13:54310 +2015-07-29 21:01:45,071 - INFO [CommitProcessor:3:ZooKeeperServer@595] - Established session 0x34ed9ac1c1e0007 with negotiated timeout 10000 for client /10.10.34.12:59224 +2015-07-29 21:34:44,640 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.12:59230; will be dropped if server is in r-o mode +2015-07-29 21:34:46,432 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.12:59235 +2015-07-29 21:34:47,040 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.17:51260 +2015-07-29 23:02:33,103 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.38:43508 +2015-07-29 23:05:05,988 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-29 23:42:53,384 - INFO [CommitProcessor:3:ZooKeeperServer@595] - Established session 0x34ed9ac1c1e002e with negotiated timeout 10000 for client /10.10.34.42:39469 +2015-07-29 23:44:22,733 - INFO [CommitProcessor:3:ZooKeeperServer@595] - Established session 0x34ed9ac1c1e0036 with negotiated timeout 10000 for client /10.10.34.36:37583 +2015-07-29 23:44:23,034 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.39:45022 +2015-07-29 23:52:09,561 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.41:54923 +2015-07-30 14:38:37,500 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.11:35811 +2015-07-30 14:48:54,960 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-30 14:52:35,531 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.11:37021 +2015-07-30 15:13:40,916 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.12:59284 which had sessionid 0x34ed9ac1c1e0059 +2015-07-30 15:13:40,916 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-30 15:13:49,197 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.13:54387 +2015-07-30 15:13:54,423 - INFO [CommitProcessor:3:ZooKeeperServer@595] - Established session 0x34ed9ac1c1e0064 with negotiated timeout 10000 for client /10.10.34.11:37111 +2015-07-30 15:14:15,378 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.11:37116; will be dropped if server is in r-o mode +2015-07-30 15:32:23,858 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.11:37330 +2015-07-30 16:18:14,811 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.18:46783 which had sessionid 0x34ed9ac1c1e0086 +2015-07-30 16:18:36,028 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.11:40581 which had sessionid 0x34ed9ac1c1e0093 +2015-07-30 16:21:13,810 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-30 16:21:27,293 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.12:59323 +2015-07-30 16:34:25,605 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.13:54616; will be dropped if server is in r-o mode +2015-07-30 16:34:35,580 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.14:49822; will be dropped if server is in r-o mode +2015-07-30 16:36:05,149 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.11:41160 which had sessionid 0x34ed9ac1c1e00a9 +2015-07-30 17:11:56,508 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.12:59359 +2015-07-30 17:22:36,450 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.13:54649 +2015-07-30 17:34:50,730 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.11:41732 +2015-07-30 17:36:52,812 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-30 17:40:45,765 - WARN [RecvWorker:1:QuorumCnxManager$RecvWorker@762] - Connection broken for id 1, my id = 3, error = +2015-07-30 17:49:01,419 - INFO [CommitProcessor:3:ZooKeeperServer@595] - Established session 0x34ed9ac1c1e00d1 with negotiated timeout 10000 for client /10.10.34.11:49255 +2015-07-30 17:57:38,413 - INFO [QuorumPeer[myid=3]/0:0:0:0:0:0:0:0:2181:QuorumPeer@670] - LOOKING +2015-07-30 17:57:38,440 - INFO [WorkerReceiver[myid=3]:FastLeaderElection@542] - Notification: 3 (n.leader), 0x100001564 (n.zxid), 0x3 (n.round), FOLLOWING (n.state), 3 (n.sid), 0x2 (n.peerEPoch), FOLLOWING (my state) +2015-07-30 17:58:23,837 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.13:50180 +2015-07-30 19:19:12,507 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.11:50716; will be dropped if server is in r-o mode +2015-07-30 19:35:00,232 - INFO [CommitProcessor:3:ZooKeeperServer@595] - Established session 0x34ede65503f0025 with negotiated timeout 10000 for client /10.10.34.11:50961 +2015-07-30 19:35:00,326 - INFO [CommitProcessor:3:ZooKeeperServer@595] - Established session 0x34ede65503f0027 with negotiated timeout 10000 for client /10.10.34.12:56359 +2015-07-30 19:57:45,009 - INFO [CommitProcessor:3:ZooKeeperServer@595] - Established session 0x34ede65503f002d with negotiated timeout 20000 for client /10.10.34.11:51041 +2015-07-30 19:57:45,045 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.11:51043; will be dropped if server is in r-o mode +2015-07-30 19:59:02,357 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.11:51097 +2015-07-30 19:59:02,549 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.13:50224 +2015-07-30 20:06:22,905 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.11:51097 which had sessionid 0x34ede65503f002f +2015-07-30 20:06:22,989 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.12:56372 which had sessionid 0x34ede65503f0030 +2015-07-30 20:14:09,840 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.11:51393 +2015-07-30 20:36:32,026 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.12:56424; will be dropped if server is in r-o mode +2015-07-30 20:36:32,135 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.13:50253 +2015-07-30 21:01:49,990 - INFO [CommitProcessor:3:ZooKeeperServer@595] - Established session 0x34ede65503f0058 with negotiated timeout 20000 for client /10.10.34.11:51967 +2015-07-30 23:03:42,330 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-30 23:52:53,800 - INFO [main:QuorumPeer@933] - minSessionTimeout set to -1 +2015-07-30 23:52:57,092 - INFO [QuorumPeer[myid=3]/0:0:0:0:0:0:0:0:2181:Environment@100] - Server environment:os.name=Linux +2015-07-30 23:52:57,093 - INFO [QuorumPeer[myid=3]/0:0:0:0:0:0:0:0:2181:Environment@100] - Server environment:user.name=zookeeper +2015-07-31 00:02:53,198 - INFO [CommitProcessor:3:ZooKeeperServer@595] - Established session 0x34edfaa9c220002 with negotiated timeout 10000 for client /10.10.34.11:53000 +2015-07-31 00:02:56,431 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.24:37975 +2015-07-31 00:02:57,579 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.39:51758 +2015-07-31 00:15:23,611 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.11:53310 which had sessionid 0x34edfaa9c220012 +2015-07-31 00:16:12,152 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@349] - caught end of stream exception +2015-07-31 00:17:54,495 - INFO [CommitProcessor:3:ZooKeeperServer@595] - Established session 0x34edfaa9c22001e with negotiated timeout 10000 for client /10.10.34.41:51908 +2015-07-31 11:07:41,903 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.13:42060 which had sessionid 0x34edfaa9c22002d +2015-07-31 11:09:00,683 - INFO [CommitProcessor:3:ZooKeeperServer@595] - Established session 0x34edfaa9c22003a with negotiated timeout 10000 for client /10.10.34.16:42267 +2015-07-31 11:09:02,264 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.34:55584; will be dropped if server is in r-o mode +2015-07-31 11:09:02,548 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@793] - Connection request from old client /10.10.34.37:34701; will be dropped if server is in r-o mode +2015-07-31 15:15:17,186 - INFO [/10.10.34.13:3888:QuorumCnxManager$Listener@493] - Received connection request /10.10.34.11:53230 +2015-07-31 15:36:23,686 - INFO [main:QuorumPeer@933] - minSessionTimeout set to -1 +2015-07-31 15:36:23,865 - INFO [QuorumPeer[myid=3]/0:0:0:0:0:0:0:0:2181:Environment@100] - Server environment:java.home=/usr/lib/jvm/java-7-openjdk-amd64/jre +2015-07-31 15:36:23,884 - INFO [QuorumPeer[myid=3]/0:0:0:0:0:0:0:0:2181:Learner@325] - Getting a snapshot from leader +2015-07-31 21:24:18,366 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.11:59186 which had sessionid 0x34ee30a5c530018 +2015-07-31 21:32:18,447 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxnFactory@197] - Accepted socket connection from /10.10.34.23:51828 +2015-07-31 21:32:19,994 - INFO [CommitProcessor:3:ZooKeeperServer@595] - Established session 0x34ee30a5c53002b with negotiated timeout 10000 for client /10.10.34.42:37429 +2015-08-07 07:27:46,402 - INFO [WorkerReceiver[myid=3]:FastLeaderElection@542] - Notification: 3 (n.leader), 0x700000197 (n.zxid), 0x1 (n.round), LOOKING (n.state), 3 (n.sid), 0x7 (n.peerEPoch), LOOKING (my state) +2015-08-10 17:52:39,698 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@839] - Client attempting to establish new session at /10.10.34.13:58180 +2015-08-10 17:53:14,914 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@1001] - Closed socket connection for client /10.10.34.12:33342 which had sessionid 0x34f0557885e0002 +2015-08-10 17:53:16,001 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x14f05578bd80006, timeout of 10000ms exceeded +2015-08-10 18:12:34,001 - INFO [SessionTracker:ZooKeeperServer@325] - Expiring session 0x14f05578bd8000f, timeout of 10000ms exceeded +2015-08-10 18:12:34,004 - INFO [ProcessThread(sid:3 cport:-1)::PrepRequestProcessor@476] - Processed session termination for sessionid: 0x24f0557806a0010 \ No newline at end of file diff --git a/2026/day-20/day-20-solution.md b/2026/day-20/day-20-solution.md new file mode 100644 index 0000000000..cdd18da465 --- /dev/null +++ b/2026/day-20/day-20-solution.md @@ -0,0 +1,441 @@ +# Day 20 – Log Analyzer and Report Generator + +## Overview + +A Bash script that ingests a server log file, extracts key metrics with `awk`, `grep`, `sort`, and `uniq`, then writes a formatted summary report. An optional archive feature moves the processed log into a timestamped `archive/` directory. + +--- + +## Script: `log_analyzer.sh` + +```bash +#!/usr/bin/env bash +# ============================================================================= +# log_analyzer.sh – Day 20 Bash Scripting Challenge +# Analyzes a log file and generates a daily summary report. +# ============================================================================= + +set -euo pipefail + +# ─── Colour helpers ────────────────────────────────────────────────────────── +RED='\033[0;31m'; YELLOW='\033[1;33m'; GREEN='\033[0;32m' +CYAN='\033[0;36m'; BOLD='\033[1m'; RESET='\033[0m' + +# ─── Task 1 : Input & Validation ───────────────────────────────────────────── +if [[ $# -lt 1 ]]; then + echo -e "${RED}[ERROR]${RESET} No log file provided." + echo "Usage: $0 " + exit 1 +fi + +LOG_FILE="$1" + +if [[ ! -f "$LOG_FILE" ]]; then + echo -e "${RED}[ERROR]${RESET} File not found: '$LOG_FILE'" + exit 1 +fi + +REPORT_DATE=$(date +%Y-%m-%d) +REPORT_FILE="log_report_${REPORT_DATE}.txt" + +echo -e "${BOLD}${CYAN}========================================${RESET}" +echo -e "${BOLD}${CYAN} Log Analyzer – $(date '+%Y-%m-%d %H:%M:%S')${RESET}" +echo -e "${BOLD}${CYAN}========================================${RESET}" +echo "" + +# ─── Task 2 : Error Count ──────────────────────────────────────────────────── +# awk counts lines that contain ERROR or Failed (case-sensitive) +TOTAL_ERRORS=$(awk '/ERROR|Failed/{count++} END{print count+0}' "$LOG_FILE") +TOTAL_LINES=$(awk 'END{print NR}' "$LOG_FILE") + +echo -e "${BOLD}Total lines processed :${RESET} $TOTAL_LINES" +echo -e "${BOLD}Total errors (ERROR|Failed) :${RESET} ${RED}${TOTAL_ERRORS}${RESET}" +echo "" + +# ─── Task 3 : Critical Events ──────────────────────────────────────────────── +echo -e "${YELLOW}--- Critical Events ---${RESET}" + +# awk prints line number + content for every CRITICAL line +CRITICAL_LINES=$(awk '/CRITICAL/{printf "Line %d: %s\n", NR, $0}' "$LOG_FILE") + +if [[ -z "$CRITICAL_LINES" ]]; then + echo " (none found)" +else + echo "$CRITICAL_LINES" +fi +echo "" + +# ─── Task 4 : Top 5 Error Messages ────────────────────────────────────────── +echo -e "${YELLOW}--- Top 5 Error Messages ---${RESET}" + +# awk extracts the "message" portion (fields 4 onward) from ERROR lines, +# then sort | uniq -c | sort -rn ranks by frequency. +TOP5=$(awk '/ERROR/{ + msg = "" + for (i=4; i<=NF; i++) msg = (msg == "" ? $i : msg " " $i) + print msg +}' "$LOG_FILE" \ + | sort \ + | uniq -c \ + | sort -rn \ + | head -5 \ + | awk '{cnt=$1; $1=""; sub(/^ /,""); printf "%-5s %s\n", cnt, $0}') + +if [[ -z "$TOP5" ]]; then + echo " (no ERROR lines found)" +else + echo "$TOP5" +fi +echo "" + +# ─── Task 5 : Generate Summary Report ─────────────────────────────────────── +{ + echo "============================================" + echo " LOG ANALYSIS REPORT" + echo " Generated : $(date '+%Y-%m-%d %H:%M:%S')" + echo "============================================" + echo "" + echo "Log File : $LOG_FILE" + echo "Analysis Date : $REPORT_DATE" + echo "Total Lines : $TOTAL_LINES" + echo "Total Errors : $TOTAL_ERRORS" + echo "" + echo "--------------------------------------------" + echo "Top 5 Error Messages" + echo "--------------------------------------------" + if [[ -z "$TOP5" ]]; then + echo " (no ERROR lines found)" + else + echo "$TOP5" + fi + echo "" + echo "--------------------------------------------" + echo "Critical Events" + echo "--------------------------------------------" + if [[ -z "$CRITICAL_LINES" ]]; then + echo " (none found)" + else + echo "$CRITICAL_LINES" + fi + echo "" + echo "============================================" + echo " END OF REPORT" + echo "============================================" +} > "$REPORT_FILE" + +echo -e "${GREEN}[OK]${RESET} Report saved → ${BOLD}${REPORT_FILE}${RESET}" +echo "" + +# ─── Task 6 (Optional) : Archive Processed Log ─────────────────────────────── +ARCHIVE_DIR="archive" + +read -r -p "Archive '$LOG_FILE' to ./${ARCHIVE_DIR}/? [y/N] " ARCHIVE_CHOICE +case "${ARCHIVE_CHOICE,,}" in + y|yes) + mkdir -p "$ARCHIVE_DIR" + mv "$LOG_FILE" "$ARCHIVE_DIR/" + echo -e "${GREEN}[OK]${RESET} Log archived → ${BOLD}${ARCHIVE_DIR}/$(basename "$LOG_FILE")${RESET}" + ;; + *) + echo "Skipping archive." + ;; +esac + +echo "" +echo -e "${BOLD}${CYAN}Analysis complete.${RESET}" +``` + +--- + +## Sample Output + +Running against `sample_log.log` (50 lines, mixed INFO / ERROR / CRITICAL / Failed): + +``` +======================================== + Log Analyzer – 2026-02-28 09:54:16 +======================================== + +Total lines processed : 50 +Total errors (ERROR|Failed) : 33 + +--- Critical Events --- +Line 27: 2025-07-29 09:08:27 CRITICAL Disk space below threshold (usage: 92%) +Line 36: 2025-07-29 09:50:55 CRITICAL Database connection lost (host: db-primary:5432) +Line 47: 2025-07-29 10:45:52 CRITICAL CPU temperature exceeded safe limit (98°C) + +--- Top 5 Error Messages --- +7 Connection timed out for host 192.168.1.10 +3 File not found: /var/data/config.yml +3 Disk I/O error on /dev/sda1 +2 File not found: /tmp/session_cache +2 Connection timed out for host 10.0.0.5 + +[OK] Report saved → log_report_2026-02-28.txt +``` + +### Generated report (`log_report_2026-02-28.txt`) + +``` +============================================ + LOG ANALYSIS REPORT + Generated : 2026-02-28 09:54:16 +============================================ + +Log File : sample_log.log +Analysis Date : 2026-02-28 +Total Lines : 50 +Total Errors : 33 + +-------------------------------------------- +Top 5 Error Messages +-------------------------------------------- +7 Connection timed out for host 192.168.1.10 +3 File not found: /var/data/config.yml +3 Disk I/O error on /dev/sda1 +2 File not found: /tmp/session_cache +2 Connection timed out for host 10.0.0.5 + +-------------------------------------------- +Critical Events +-------------------------------------------- +Line 27: 2025-07-29 09:08:27 CRITICAL Disk space below threshold (usage: 92%) +Line 36: 2025-07-29 09:50:55 CRITICAL Database connection lost (host: db-primary:5432) +Line 47: 2025-07-29 10:45:52 CRITICAL CPU temperature exceeded safe limit (98°C) + +============================================ + END OF REPORT +============================================ +``` + +--- + +## Tools & Commands Used + +| Tool | Purpose | +|------|---------| +| `awk` | Count lines, extract fields, print with line numbers, format output | +| `sort` | Alphabetically sort extracted messages before counting | +| `uniq -c` | Count consecutive duplicate lines | +| `sort -rn` | Sort numerically in descending order (highest count first) | +| `head -5` | Limit output to top 5 results | +| `date` | Generate the report filename and timestamp | +| `mkdir -p` | Create archive directory safely (no error if exists) | +| `mv` | Move the processed log into the archive | + +### Key `awk` patterns used + +```bash +# Count matching lines +awk '/ERROR|Failed/{count++} END{print count+0}' file + +# Count all lines +awk 'END{print NR}' file + +# Print line number + full line for matches +awk '/CRITICAL/{printf "Line %d: %s\n", NR, $0}' file + +# Extract message (fields 4 onward) from ERROR lines +awk '/ERROR/{ + msg = "" + for (i=4; i<=NF; i++) msg = (msg == "" ? $i : msg " " $i) + print msg +}' file + +# Reformat uniq -c output (left-align count, strip leading space) +awk '{cnt=$1; $1=""; sub(/^ /,""); printf "%-5s %s\n", cnt, $0}' +``` + +--- + +## 3 Key Learnings + +1. **`awk` is a complete text-processing language inside Bash.** Using `NR` for line numbers, `NF` for field counts, and looping over `$i` fields makes it possible to replace many `grep | cut | sed` pipelines with a single, readable `awk` block. + +2. **`sort | uniq -c | sort -rn` is the canonical frequency-ranking pipeline.** The first `sort` is required to bring identical lines together (since `uniq` only collapses *adjacent* duplicates); `uniq -c` prefixes each unique line with its count; `sort -rn` then orders by count descending. + +3. **`set -euo pipefail` makes scripts production-safe.** `-e` exits on any command failure, `-u` treats unset variables as errors, and `-o pipefail` catches failures in the middle of a pipeline — together they prevent silent bugs where a script happily continues after a critical step fails. + +--- + +## Files + +``` +2026/day-20/ +├── log_analyzer.sh # Main script +├── sample_log.log # Sample log for testing +├── log_report_YYYY-MM-DD.txt # Generated on each run +└── day-20-solution.md # This document +``` + +--- + +`#90DaysOfDevOps` `#DevOpsKaJosh` `#TrainWithShubham` + +## ⚙️ Script Code — `log_analyzer.sh` using grep + +```bash +#!/bin/bash + +# ---- Input Validation ---- + +if [ $# -eq 0 ]; then + echo "Error: Please provide a log file path." + echo "Usage: $0 " + exit 1 +fi + +LOG_FILE="$1" + +if [ ! -f "$LOG_FILE" ]; then + echo "Error: File does not exist: $LOG_FILE" + exit 1 +fi + +DATE=$(date +%Y-%m-%d) +REPORT="log_report_${DATE}.txt" + +echo "Analyzing log file: $LOG_FILE" + +# ---- Error Count ---- + +ERROR_COUNT=$(grep -E "ERROR|Failed" "$LOG_FILE" | wc -l) + +echo "Total Errors: $ERROR_COUNT" + +# ---- Critical Events ---- + +echo +echo "--- Critical Events ---" + +CRITICAL_OUTPUT=$(grep -n "CRITICAL" "$LOG_FILE") + +if [ -z "$CRITICAL_OUTPUT" ]; then + echo "No critical events found." +else + echo "$CRITICAL_OUTPUT" | sed 's/^/Line /' +fi + +# ---- Top 5 Error Messages ---- + +echo +echo "--- Top 5 Error Messages ---" + +TOP_ERRORS=$(grep "ERROR" "$LOG_FILE" \ + | awk '{$1=$2=$3=""; sub(/^ +/, ""); print}' \ + | sort \ + | uniq -c \ + | sort -rn \ + | head -5) + +echo "$TOP_ERRORS" + +# ---- Generate Report ---- + +TOTAL_LINES=$(wc -l < "$LOG_FILE") + +{ + echo "===== Log Analysis Report =====" + echo "Date: $DATE" + echo "Log File: $LOG_FILE" + echo "Total Lines: $TOTAL_LINES" + echo "Total Errors: $ERROR_COUNT" + echo + + echo "--- Top 5 Error Messages ---" + echo "$TOP_ERRORS" + echo + + echo "--- Critical Events ---" + if [ -z "$CRITICAL_OUTPUT" ]; then + echo "No critical events found." + else + echo "$CRITICAL_OUTPUT" | sed 's/^/Line /' + fi + +} > "$REPORT" + +echo +echo "Report generated: $REPORT" + +# ---- Archive Processed Logs (Optional) ---- + +ARCHIVE_DIR="archive" +mkdir -p "$ARCHIVE_DIR" +mv "$LOG_FILE" "$ARCHIVE_DIR/" + +echo "Log file moved to $ARCHIVE_DIR/" +``` + +--- + +## ▶️ How to Run + +```bash +chmod +x log_analyzer.sh +./log_analyzer.sh sample.logs +``` + +--- + +## 🖥️ Sample Console Output + +``` +Analyzing log file: sample.logs + +Total Errors: 23 + +--- Critical Events --- +Line 1: 2026-02-27 15:40:34 [CRITICAL] - 3479 +Line 3: 2026-02-27 15:40:34 [CRITICAL] - 27031 +... + +--- Top 5 Error Messages --- +8 Disk full +5 Segmentation fault +4 Out of memory +3 Invalid input +2 Failed to connect + +Report generated: log_report_2026-02-27.txt +Log file moved to archive/ +``` + +--- + +## 📊 Generated Report Sample + +**File:** `log_report_2026-02-27.txt` + +``` +===== Log Analysis Report ===== +Date: 2026-02-27 +Log File: sample.logs +Total Lines: 100 +Total Errors: 23 + +--- Top 5 Error Messages --- +8 Disk full +5 Segmentation fault +4 Out of memory +3 Invalid input +2 Failed to connect + +--- Critical Events --- +Line 1: 2026-02-27 15:40:34 [CRITICAL] - 3479 +Line 3: 2026-02-27 15:40:34 [CRITICAL] - 27031 +... +``` + +--- + +## 🧰 Tools & Commands Used + +* **grep** → Pattern searching +* **awk** → Text processing +* **sort** → Sorting output +* **uniq -c** → Counting occurrences +* **wc -l** → Line counting +* **sed** → Formatting output +* **date** → Dynamic report filename +* **mkdir / mv** → File management diff --git a/2026/day-21/shell_scripting_cheatsheet.md b/2026/day-21/shell_scripting_cheatsheet.md new file mode 100644 index 0000000000..9d18d814e6 --- /dev/null +++ b/2026/day-21/shell_scripting_cheatsheet.md @@ -0,0 +1,469 @@ +# Shell Scripting Cheat Sheet + +## Quick Reference Table + +| Topic | Key Syntax | Example | +|-------|-----------|---------| +| Variable | `VAR="value"` | `NAME="DevOps"` | +| Argument | `$1`, `$2` | `./script.sh arg1` | +| If | `if [ condition ]; then` | `if [ -f file ]; then` | +| For loop | `for i in list; do` | `for i in 1 2 3; do` | +| Function | `name() { ... }` | `greet() { echo "Hi"; }` | +| Grep | `grep pattern file` | `grep -i "error" log.txt` | +| Awk | `awk '{print $1}' file` | `awk -F: '{print $1}' /etc/passwd` | +| Sed | `sed 's/old/new/g' file` | `sed -i 's/foo/bar/g' config.txt` | +| Exit code | `$?` | `echo $? # 0=success` | +| Trap | `trap 'fn' EXIT` | `trap 'rm -f /tmp/lock' EXIT` | + +--- + +## 1. Basics + +### Shebang +Tells the OS which interpreter to use. Must be the first line. +```bash +#!/bin/bash +``` + +### Running a Script +```bash +chmod +x script.sh # make executable +./script.sh # run directly +bash script.sh # run with bash explicitly +``` + +### Comments +```bash +# This is a full-line comment +echo "Hello" # inline comment +``` + +### Variables +```bash +NAME="DevOps" # declare (no spaces around =) +echo $NAME # use variable +echo "$NAME" # quoted — safe, prevents word splitting +echo '$NAME' # single quotes — literal, no expansion +``` + +### Reading User Input +```bash +read -p "Enter your name: " USERNAME +echo "Hello, $USERNAME" +``` + +### Command-Line Arguments +```bash +$0 # script name +$1 # first argument +$# # number of arguments +$@ # all arguments (as separate words) +$? # exit code of last command +``` + +--- + +## 2. Operators and Conditionals + +### String Comparisons +```bash +[ "$a" = "$b" ] # equal +[ "$a" != "$b" ] # not equal +[ -z "$a" ] # true if string is empty +[ -n "$a" ] # true if string is non-empty +``` + +### Integer Comparisons +```bash +[ $a -eq $b ] # equal +[ $a -ne $b ] # not equal +[ $a -lt $b ] # less than +[ $a -gt $b ] # greater than +[ $a -le $b ] # less than or equal +[ $a -ge $b ] # greater than or equal +``` + +### File Test Operators +```bash +[ -f file ] # is a regular file +[ -d dir ] # is a directory +[ -e path ] # exists +[ -r file ] # readable +[ -w file ] # writable +[ -x file ] # executable +[ -s file ] # exists and non-empty +``` + +### if / elif / else +```bash +if [ "$1" = "start" ]; then + echo "Starting..." +elif [ "$1" = "stop" ]; then + echo "Stopping..." +else + echo "Unknown command" +fi +``` + +### Logical Operators +```bash +[ condition1 ] && [ condition2 ] # AND +[ condition1 ] || [ condition2 ] # OR +! [ condition ] # NOT +``` + +### Case Statement +```bash +case "$1" in + start) echo "Starting" ;; + stop) echo "Stopping" ;; + *) echo "Usage: $0 {start|stop}" ;; +esac +``` + +--- + +## 3. Loops + +### for Loop +```bash +# List-based +for fruit in apple banana cherry; do + echo "$fruit" +done + +# C-style +for ((i=1; i<=5; i++)); do + echo "$i" +done +``` + +### while Loop +```bash +count=1 +while [ $count -le 5 ]; do + echo "$count" + ((count++)) +done +``` + +### until Loop +```bash +count=1 +until [ $count -gt 5 ]; do + echo "$count" + ((count++)) +done +``` + +### Loop Control +```bash +break # exit loop immediately +continue # skip to next iteration +``` + +### Loop Over Files +```bash +for file in *.log; do + echo "Processing $file" +done +``` + +### Loop Over Command Output +```bash +cat servers.txt | while read line; do + echo "Pinging $line" +done +``` + +--- + +## 4. Functions + +### Define and Call +```bash +greet() { + echo "Hello, $1!" +} + +greet "DevOps" # call with argument +``` + +### Arguments Inside Functions +```bash +add() { + echo $(( $1 + $2 )) +} +add 3 5 # outputs 8 +``` + +### Return Values +```bash +# return sends an exit code (0-255) +is_even() { + [ $(( $1 % 2 )) -eq 0 ] && return 0 || return 1 +} + +# echo is used to return actual data +get_date() { + echo "$(date +%Y-%m-%d)" +} +TODAY=$(get_date) +``` + +### Local Variables +```bash +my_func() { + local x=10 # scoped to this function only + echo "$x" +} +``` + +--- + +## 5. Text Processing Commands + +### grep — Search Patterns +```bash +grep "error" file.log # basic search +grep -i "error" file.log # case-insensitive +grep -r "error" ./logs/ # recursive +grep -c "error" file.log # count matching lines +grep -n "error" file.log # show line numbers +grep -v "error" file.log # invert (exclude matches) +grep -E "err|warn" file.log # extended regex (OR) +``` + +### awk — Column Processing +```bash +awk '{print $1}' file # print first column +awk -F: '{print $1}' /etc/passwd # custom field separator +awk '$3 > 100 {print $1}' file # filter by condition +awk 'BEGIN {print "Start"} {print} END {print "Done"}' file +``` + +### sed — Stream Editor +```bash +sed 's/old/new/' file # replace first occurrence per line +sed 's/old/new/g' file # replace all occurrences +sed -i 's/foo/bar/g' file # in-place edit +sed '/^#/d' file # delete comment lines +sed -n '5,10p' file # print lines 5–10 +``` + +### cut — Extract Columns +```bash +cut -d',' -f1 file.csv # first field, comma-delimited +cut -d':' -f1,3 /etc/passwd # fields 1 and 3 +cut -c1-5 file # first 5 characters +``` + +### sort +```bash +sort file # alphabetical +sort -n file # numerical +sort -r file # reverse +sort -u file # unique (remove duplicates) +sort -k2 file # sort by second column +``` + +### uniq +```bash +uniq file # remove consecutive duplicates (sort first!) +uniq -c file # count occurrences +uniq -d file # show only duplicates +``` + +### tr — Translate / Delete Characters +```bash +echo "hello" | tr 'a-z' 'A-Z' # uppercase +echo "he llo" | tr -d ' ' # delete spaces +echo "aabbcc" | tr -s 'a-z' # squeeze repeated chars +``` + +### wc — Count +```bash +wc -l file # line count +wc -w file # word count +wc -c file # byte count +``` + +### head / tail +```bash +head -n 20 file # first 20 lines +tail -n 20 file # last 20 lines +tail -f /var/log/syslog # follow (live updates) +tail -f app.log | grep "ERROR" # follow + filter +``` + +--- + +## 6. Useful One-Liners + +```bash +# Find and delete files older than 30 days +find /var/logs -name "*.log" -mtime +30 -delete + +# Count total lines across all .log files +wc -l *.log | tail -1 + +# Replace a string across multiple files +sed -i 's/localhost/prod-server/g' *.conf + +# Check if a service is running +systemctl is-active --quiet nginx && echo "Running" || echo "Stopped" + +# Alert if disk usage exceeds 80% +df -h | awk '$5+0 > 80 {print "ALERT: "$0}' + +# Parse CSV — print second column +awk -F',' '{print $2}' data.csv + +# Tail a log and filter for errors in real time +tail -f app.log | grep --line-buffered "ERROR" + +# List top 10 most used commands from history +history | awk '{print $2}' | sort | uniq -c | sort -rn | head -10 + +# Kill all processes matching a name +pkill -f "python app.py" +``` + +--- + +## 7. Error Handling and Debugging + +### Exit Codes +```bash +$? # exit code of last command (0 = success) +exit 0 # explicit success +exit 1 # explicit failure +``` + +### Strict Mode Options +```bash +set -e # exit immediately on error +set -u # treat unset variables as errors +set -o pipefail # catch errors inside pipes +set -x # debug mode — print each command before executing + +# Common pattern — use all together at top of script: +set -euo pipefail +``` + +### Trap — Cleanup on Exit +```bash +cleanup() { + rm -f /tmp/mylock + echo "Cleanup done" +} +trap cleanup EXIT # runs on exit (normal or error) +trap 'echo "Interrupted"' INT # runs on Ctrl+C +``` + +### Defensive Checks +```bash +# Check required argument +if [ $# -lt 1 ]; then + echo "Usage: $0 " >&2 + exit 1 +fi + +# Check if command exists +command -v docker &>/dev/null || { echo "docker not found"; exit 1; } + +# Default value if variable unset +LOG_DIR="${LOG_DIR:-/var/log/myapp}" +``` + +5. Text Processing Commands +grep — Top 10 Production Commands +bash# 1. Find all ERROR/WARN lines in app logs (case-insensitive) +grep -iE "error|warn|critical" /var/log/app/app.log + +# 2. Search recursively across all config files for a setting +grep -r "max_connections" /etc/nginx/ + +# 3. Show filename + line number — great for multi-file log triage +grep -rn "OutOfMemoryError" /var/log/tomcat/ + +# 4. Exclude noise (filter out debug/info, keep real issues) +grep -v -E "DEBUG|INFO" /var/log/app/app.log + +# 5. Count how many times a pattern appears (quick error frequency check) +grep -c "Connection refused" /var/log/app/app.log + +# 6. Live log monitoring — tail + grep for errors in real time +tail -f /var/log/nginx/access.log | grep --line-buffered " 50[0-9] " + +# 7. Extract only matching part (e.g. IP addresses from access logs) +grep -oE "\b([0-9]{1,3}\.){3}[0-9]{1,3}\b" /var/log/nginx/access.log | sort | uniq -c | sort -rn + +# 8. Search inside .gz compressed logs without decompressing +zgrep "ERROR" /var/log/app/app.log.2.gz + +# 9. Show N lines of context around a match (before/after the error) +grep -A 5 -B 2 "FATAL" /var/log/app/app.log + +# 10. Find all files containing a pattern (just filenames, no content) +grep -rl "password=" /etc/ 2>/dev/null +awk — Top 10 Production Commands +bash# 1. Print specific columns from logs (e.g. timestamp + log level) +awk '{print $1, $2, $3}' /var/log/app/app.log + +# 2. Calculate average response time from access logs +awk '{sum += $NF; count++} END {print "Avg:", sum/count, "ms"}' response_times.log + +# 3. Filter lines where HTTP status is 5xx (column 9 in nginx logs) +awk '$9 >= 500 {print $0}' /var/log/nginx/access.log + +# 4. Parse /etc/passwd to list all system users and their shells +awk -F: '$3 >= 1000 {print $1, $7}' /etc/passwd + +# 5. Sum disk usage of a specific user from du output +du -sh /home/* | awk '{sum += $1} END {print "Total:", sum, "MB"}' + +# 6. Find top 10 IPs hammering your server +awk '{print $1}' /var/log/nginx/access.log | sort | uniq -c | sort -rn | head -10 + +# 7. Print lines between two patterns (e.g. extract a specific deploy block) +awk '/Deploy START/,/Deploy END/' /var/log/deploy.log + +# 8. Alert if CPU column exceeds threshold in a monitoring output +ps aux | awk '$3 > 80 {print "HIGH CPU:", $1, $2, $3"%"}' + +# 9. Reformat CSV — swap columns and change delimiter +awk -F',' '{print $2 "|" $1 "|" $3}' data.csv + +# 10. Count occurrences of each HTTP status code +awk '{print $9}' /var/log/nginx/access.log | sort | uniq -c | sort -rn +sed — Top 10 Production Commands +bash# 1. Replace a config value in-place (e.g. update DB host during deploy) +sed -i 's/db_host=localhost/db_host=prod-db.internal/g' app.conf + +# 2. Comment out a line matching a pattern (disable a config option) +sed -i 's/^PermitRootLogin yes/#PermitRootLogin yes/' /etc/ssh/sshd_config + +# 3. Uncomment a line (enable a config option) +sed -i 's/^#\(MaxConnections\)/\1/' /etc/app/config.conf + +# 4. Delete all blank lines from a file +sed -i '/^[[:space:]]*$/d' config.conf + +# 5. Delete all comment lines (clean up config for review) +sed '/^#/d' /etc/app/config.conf + +# 6. Insert a line after a match (e.g. add config option after a section header) +sed -i '/\[database\]/a db_timeout=30' app.ini + +# 7. Print only lines 100–200 of a huge log file (faster than head/tail combo) +sed -n '100,200p' /var/log/app/app.log + +# 8. Remove ANSI color codes from logs (clean up CI/CD output) +sed -i 's/\x1B\[[0-9;]*[mK]//g' build.log + +# 9. Replace a port number across multiple files in a directory +find /etc/nginx/conf.d/ -name "*.conf" | xargs sed -i 's/:8080/:9090/g' + +# 10. Bulk rename — strip a prefix from lines (useful in pipeline transformations) +sed 's/^prod-//' servers.txt \ No newline at end of file diff --git a/2026/day-22/day-22-notes.md b/2026/day-22/day-22-notes.md new file mode 100644 index 0000000000..392414ae55 --- /dev/null +++ b/2026/day-22/day-22-notes.md @@ -0,0 +1,150 @@ +# Day 22 – Git Notes & Reflections + +## Task 1: Install and Configure Git + +```bash +# Verify Git is installed +git --version +# Output: git version 2.43.0 (or similar) + +# Set up identity +git config --global user.name "Your Name" +git config --global user.email "you@example.com" + +# Verify configuration +git config --list +``` + +--- + +## Task 2: Create Your Git Project + +```bash +mkdir devops-git-practice +cd devops-git-practice +git init +git status +ls -la .git/ +``` + +**What's inside `.git/`?** + +``` +.git/ +├── HEAD → points to the current branch (e.g., refs/heads/main) +├── config → repository-specific settings +├── description → used by GitWeb (not important locally) +├── hooks/ → scripts that run before/after Git events (e.g., pre-commit) +├── info/ → contains .gitignore patterns for this repo only +├── objects/ → where Git stores ALL your data (commits, trees, blobs) +└── refs/ → pointers to commit hashes (branches, tags) +``` + +The `.git/` folder is Git's brain — it stores the entire history and configuration of your repository. + +--- + +## Task 4: Stage and Commit + +```bash +git add git-commands.md # Stage the file +git status # Verify what's staged +git commit -m "Initial commit: add git-commands reference" +git log # View commit history +``` + +--- + +## Task 5: Build Commit History + +```bash +# After editing git-commands.md: +git diff # See what changed +git add git-commands.md +git commit -m "Add viewing changes section to git-commands" + +# Repeat for more commits... +git log --oneline # Compact history view +``` + +--- + +## Task 6: Conceptual Questions + +### 1. What is the difference between `git add` and `git commit`? + +`git add` moves changes from your **working directory** into the **staging area** — it's like placing items into a box before sealing it. `git commit` seals that box and permanently records it in the repository's history with a timestamp and message. You must `add` before you can `commit`; they are two separate, deliberate steps. + +--- + +### 2. What does the staging area do? Why doesn't Git just commit directly? + +The staging area (also called the "index") acts as a buffer between your work and your commit history. It lets you: + +- **Selectively commit** — you might have changed 5 files but only want to commit 2 of them in this snapshot. +- **Review before committing** — you can inspect exactly what will go into the commit using `git diff --staged`. +- **Build meaningful commits** — group related changes together into one logical commit even if you made them at different times. + +If Git committed every saved file immediately, your history would be noisy and hard to reason about. The staging area gives you intentional control. + +--- + +### 3. What information does `git log` show you? + +`git log` shows the complete commit history of the repository, displayed from newest to oldest. For each commit it shows: + +- **Commit hash** — a unique 40-character SHA-1 identifier (e.g., `a3f8c2d...`) +- **Author** — the name and email of who made the commit +- **Date** — when the commit was recorded +- **Commit message** — the description written by the author + +With flags like `--oneline` it compresses this to one line per commit; `--graph` adds an ASCII tree of branches. + +--- + +### 4. What is the `.git/` folder and what happens if you delete it? + +The `.git/` folder is the **entire Git repository**. It contains: +- All commit history (stored as compressed objects) +- Branch and tag references +- The staging area (index) +- Configuration and hooks + +**If you delete `.git/`**, your project folder becomes a plain directory — all Git history, branches, and metadata are permanently gone. Your current files remain intact, but there is no way to recover the history without a remote backup (e.g., on GitHub). Git would treat the folder as if it had never been initialized. + +--- + +### 5. What is the difference between a working directory, staging area, and repository? + +These are the three zones Git manages: + +| Zone | Also Called | What It Is | +|------|-------------|------------| +| **Working Directory** | Working Tree | Your actual project folder — files you see and edit on disk | +| **Staging Area** | Index / Cache | A "pre-commit" holding area where you place changes you want to include in the next commit | +| **Repository** | `.git/` directory | The permanent, compressed record of all committed snapshots in history | + +**The typical flow:** + +``` +[Edit files] → Working Directory +[git add ] → Staging Area +[git commit -m "..."] → Repository (permanent history) +``` + +Think of it like writing a letter: your draft is the working directory, your envelope (ready to seal) is the staging area, and the sent box is the repository. + +--- + +## Sample `git log --oneline` Output + +``` +f3a91bc Add undoing changes section to git-commands +7d2e04a Add viewing changes and log commands +a1c88f0 Add basic workflow commands +3b6d711 Initial commit: add git-commands reference +``` + +--- + +*Day 22 complete. Git basics are in — history, staging, and commit workflow all make sense now.* \ No newline at end of file diff --git a/2026/day-22/day-222-commands.md b/2026/day-22/day-222-commands.md new file mode 100644 index 0000000000..284c80d264 --- /dev/null +++ b/2026/day-22/day-222-commands.md @@ -0,0 +1,74 @@ +# Git Commands Reference + +> A living document of Git commands — updated daily as I learn more. +> Started: Day 22 | Last Updated: Day 22 + +--- + +## Setup & Config + +| Command | What It Does | Example | +|--------|--------------|---------| +| `git --version` | Checks the installed Git version | `git --version` → `git version 2.43.0` | +| `git config --global user.name` | Sets your global Git username | `git config --global user.name "Jane Dev"` | +| `git config --global user.email` | Sets your global Git email | `git config --global user.email "jane@example.com"` | +| `git config --list` | Lists all Git configuration settings | `git config --list` | +| `git config --global core.editor` | Sets the default editor for commit messages | `git config --global core.editor "vim"` | + +--- + +## Repository Setup + +| Command | What It Does | Example | +|--------|--------------|---------| +| `git init` | Initializes a new Git repository in the current folder | `git init` | +| `git clone` | Copies a remote repository to your local machine | `git clone https://github.com/user/repo.git` | + +--- + +## Basic Workflow + +| Command | What It Does | Example | +|--------|--------------|---------| +| `git status` | Shows the state of working directory and staging area | `git status` | +| `git add ` | Stages a specific file for the next commit | `git add git-commands.md` | +| `git add .` | Stages all changed files in the current directory | `git add .` | +| `git commit -m` | Records staged changes with a message | `git commit -m "Add git commands reference"` | +| `git commit --amend` | Modifies the most recent commit | `git commit --amend -m "Better message"` | + +--- + +## Viewing Changes + +| Command | What It Does | Example | +|--------|--------------|---------| +| `git log` | Shows the full commit history with details | `git log` | +| `git log --oneline` | Shows compact one-line commit history | `git log --oneline` | +| `git log --oneline --graph` | Shows history as an ASCII branch graph | `git log --oneline --graph` | +| `git diff` | Shows unstaged changes since the last commit | `git diff` | +| `git diff --staged` | Shows changes that are staged for commit | `git diff --staged` | +| `git show ` | Shows details and changes of a specific commit | `git show a1b2c3d` | + +--- + +## Undoing Changes + +| Command | What It Does | Example | +|--------|--------------|---------| +| `git restore ` | Discards unstaged changes in a file | `git restore notes.md` | +| `git restore --staged ` | Unstages a file (keeps changes in working dir) | `git restore --staged notes.md` | +| `git revert ` | Creates a new commit that undoes a previous commit | `git revert a1b2c3d` | + +--- + +## Exploring the Repository + +| Command | What It Does | Example | +|--------|--------------|---------| +| `ls -la .git/` | Lists the contents of the hidden .git directory | `ls -la .git/` | +| `cat .git/HEAD` | Shows which branch you're currently on | `cat .git/HEAD` | +| `cat .git/config` | Shows repository-level Git config | `cat .git/config` | + +--- + +*More commands will be added in upcoming days as new topics are covered.* \ No newline at end of file diff --git a/2026/day-23/day-23-notes.md b/2026/day-23/day-23-notes.md new file mode 100644 index 0000000000..a72112ad46 --- /dev/null +++ b/2026/day-23/day-23-notes.md @@ -0,0 +1,343 @@ +# Day 23 – Git Branching & Working with GitHub + +--- + +## Task 1: Understanding Branches + +### 1. What is a branch in Git? + +A branch is a lightweight, movable pointer to a specific commit in your repository's history. Under the hood it's just a 41-byte file in `.git/refs/heads/` that stores a commit hash. When you make a new commit on a branch, that pointer automatically advances to the new commit. + +The default branch is usually called `main` (or historically `master`). Every other branch you create diverges from some point in that history and evolves independently. + +``` +main: A → B → C + \ +feature-1: D → E +``` + +Branches `main` and `feature-1` share commits A, B, C, but only `feature-1` has D and E. + +--- + +### 2. Why do we use branches instead of committing everything to `main`? + +Committing everything directly to `main` means: +- Incomplete or broken code is immediately part of the "official" history +- Multiple people working simultaneously will constantly conflict with each other +- There's no way to experiment without risking the stable codebase +- Code review becomes impossible — there's nothing to review against + +Branches solve all of this. Each feature, bug fix, or experiment lives in its own isolated timeline. `main` only ever receives code that has been finished, tested, and reviewed. This is the foundation of every professional Git workflow (GitHub Flow, Gitflow, trunk-based development, etc.). + +--- + +### 3. What is `HEAD` in Git? + +`HEAD` is a special pointer that always tells Git *"where you are right now."* It normally points to the current branch, which in turn points to the latest commit on that branch. + +``` +HEAD → main → commit C +``` + +When you switch branches, `HEAD` moves to point at the new branch: + +``` +git switch feature-1 +HEAD → feature-1 → commit E +``` + +**Detached HEAD** is a special state where `HEAD` points directly to a commit hash instead of a branch name. This happens when you `git checkout `. Any commits you make in this state are not attached to a branch and will be garbage-collected by Git unless you create a branch from them. + +You can always check where HEAD is pointing: +```bash +cat .git/HEAD +# → ref: refs/heads/main +``` + +--- + +### 4. What happens to your files when you switch branches? + +Git replaces the contents of your working directory to match the snapshot recorded in the tip commit of the branch you're switching to. Files that exist on the new branch but not the old one appear; files that exist on the old branch but not the new one disappear; files that differ between branches are updated in place. + +Git will **refuse** to switch branches if you have uncommitted changes that would be overwritten by the switch. Your options are to: +- `git stash` — temporarily shelve your changes +- `git commit` — commit them first +- `git restore .` — discard them (destructive) + +--- + +## Task 2: Branching Commands — Hands-On + +### List all branches +```bash +git branch +# Output: +# * main ← the asterisk shows your current branch +``` + +```bash +git branch -a # Also shows remote-tracking branches +# * main +# remotes/origin/main +``` + +--- + +### Create `feature-1` and switch to it (two steps) +```bash +git branch feature-1 # Create the branch +git switch feature-1 # Switch to it +# Switched to branch 'feature-1' +``` + +--- + +### Create `feature-2` and switch in one command +```bash +git switch -c feature-2 +# Switched to a new branch 'feature-2' +``` + +> The classic equivalent is `git checkout -b feature-2`. Both do the same thing. + +--- + +### `git switch` vs `git checkout` — what's the difference? + +`git checkout` is a Swiss Army knife command introduced early in Git's history — it does too many things: +- Switch branches: `git checkout feature-1` +- Restore files: `git checkout -- file.txt` +- Detach HEAD to a commit: `git checkout a1b2c3` + +This overloading made it confusing, especially for beginners (`checkout` a file and `checkout` a branch look identical but have very different effects). + +Git 2.23 (2019) introduced two focused replacements: +- **`git switch`** — only for switching and creating branches +- **`git restore`** — only for discarding file changes + +`git switch` will refuse operations that `git checkout` would silently do in confusing ways. For day-to-day branch work, always prefer `git switch`. + +--- + +### Make a commit on `feature-1` that doesn't exist on `main` +```bash +git switch feature-1 + +# Edit a file — e.g., add a note to the bottom of git-commands.md +echo "\n## Branching (added on feature-1)" >> git-commands.md + +git add git-commands.md +git commit -m "feat: add branching section stub on feature-1" +``` + +--- + +### Switch back to `main` and verify the commit is not there +```bash +git switch main +git log --oneline + +# Output (feature-1's commit is NOT here): +# f3a91bc Add undoing changes section to git-commands +# 7d2e04a Add viewing changes and log commands +# a1c88f0 Add basic workflow commands +# 3b6d711 Initial commit: add git-commands reference +``` + +Opening `git-commands.md` in your editor confirms the branching section added on `feature-1` is absent — the file is exactly as it was on `main`. + +--- + +### Delete a branch +```bash +# Safe delete — Git refuses if the branch has unmerged commits +git branch -d feature-2 + +# Force delete — use when you intentionally want to discard unmerged work +git branch -D feature-2 +``` + +--- + +## Task 3: Push to GitHub + +### Connect local repo to GitHub remote +```bash +# After creating a new EMPTY repo on GitHub (no README, no .gitignore): +git remote add origin https://github.com//devops-git-practice.git + +# Verify the remote was added +git remote -v +# origin https://github.com//devops-git-practice.git (fetch) +# origin https://github.com//devops-git-practice.git (push) +``` + +### Push `main` to GitHub +```bash +git push -u origin main +# -u sets the upstream tracking reference so future `git push` needs no arguments +``` + +### Push `feature-1` to GitHub +```bash +git switch feature-1 +git push -u origin feature-1 +``` + +Both branches are now visible in the GitHub UI under the branch dropdown. + +--- + +### `origin` vs `upstream` — what's the difference? + +These are just **remote nicknames** (aliases for URLs). Git doesn't enforce their meaning, but the community follows a strong convention: + +| Name | Points To | When It's Used | +|------|-----------|----------------| +| `origin` | **Your own remote copy** of the repo (your GitHub repo) | Always — set automatically by `git clone` | +| `upstream` | **The original source repo** you forked from | Open-source contribution workflows | + +**Example scenario:** You fork `torvalds/linux` on GitHub. Your fork is `yourname/linux`. + +```bash +git clone https://github.com/yourname/linux.git +# origin → https://github.com/yourname/linux.git (set automatically) + +git remote add upstream https://github.com/torvalds/linux.git +# upstream → https://github.com/torvalds/linux.git (set manually) +``` + +You push your feature branches to `origin` (your fork) and open pull requests from there. You pull new updates from `upstream` (the real repo) to keep your fork current. + +--- + +## Task 4: Pull from GitHub + +### Make a change on GitHub and pull it locally +```bash +# After editing a file directly in the GitHub web editor and committing it there: + +git pull origin main +# or simply, if upstream is set: +git pull +``` + +--- + +### `git fetch` vs `git pull` — what's the difference? + +Both communicate with the remote, but they do different amounts of work: + +**`git fetch`** downloads new commits and updates remote-tracking refs (like `origin/main`) but **does not touch your working directory or current branch**. Your local `main` is unchanged. + +```bash +git fetch origin +# Updates origin/main pointer — your local main is untouched + +git log origin/main --oneline # Inspect what came down +git diff main origin/main # See what's different +git merge origin/main # Merge manually when ready +``` + +**`git pull`** is `git fetch` + `git merge` in one command. It downloads the changes and immediately merges them into your current branch. + +```bash +git pull origin main +# Equivalent to: git fetch origin && git merge origin/main +``` + +**When to use which:** + +| Scenario | Use | +|----------|-----| +| You want to see what changed before integrating | `git fetch` | +| You're on a personal branch and just want the latest | `git pull` | +| You're working in a team and want to review before merging | `git fetch` | +| Quick sync on a clean branch | `git pull` | + +The rule of thumb: `fetch` is safer and more deliberate; `pull` is faster and more convenient. + +--- + +## Task 5: Clone vs Fork + +### Clone a public repo +```bash +git clone https://github.com/github/gitignore.git +cd gitignore +git log --oneline -5 +``` + +### Fork then clone your fork +1. Go to `https://github.com/github/gitignore` in the browser +2. Click **Fork** → it creates `yourname/gitignore` on GitHub +3. Clone your fork: +```bash +git clone https://github.com/yourname/gitignore.git +cd gitignore +git remote add upstream https://github.com/github/gitignore.git +``` + +--- + +### Clone vs Fork — what's the difference? + +**Clone** is a **Git operation** — it creates a local copy of any repository on your machine. You can clone any repo you have access to. Cloning doesn't create anything on GitHub; it's purely local. You can push back only if you have write access. + +**Fork** is a **GitHub concept** (not a Git command) — it creates your own personal copy of someone else's repository *on GitHub, under your account*. You have full write access to your fork, but not to the original. Forks are how the open-source contribution model works. + +| | Clone | Fork | +|---|-------|------| +| Where it happens | Local machine | GitHub (server-side) | +| Git command? | Yes — `git clone` | No — GitHub UI or API | +| Creates GitHub repo? | No | Yes (under your account) | +| Need write access to original? | For pushing, yes | No | +| Primary use case | Working on repos you own or have access to | Contributing to someone else's project | + +--- + +### When to clone vs fork? + +**Clone** when: +- It's your own repo or your team's repo +- You have write access and will push directly + +**Fork** when: +- You want to contribute to an open-source project you don't own +- You want your own sandbox copy of a project on GitHub +- You'll submit a Pull Request back to the original + +--- + +### Keeping your fork in sync with the original + +The original repo keeps moving — new commits get added after you fork. To stay current: + +```bash +# 1. Add the original as 'upstream' (one-time setup) +git remote add upstream https://github.com/original-owner/repo.git + +# 2. Fetch new commits from upstream (doesn't touch your files) +git fetch upstream + +# 3. Merge upstream's main into your local main +git switch main +git merge upstream/main + +# 4. Push the updated main to your GitHub fork +git push origin main +``` + +This keeps your fork's `main` identical to the original. Your feature branches are unaffected until you choose to rebase or merge them. + +--- + +## Updated `git-commands.md` sections added today + +See `git-commands.md` for the new **Branching** and **Remote & GitHub** sections. + +--- + +*Day 23 complete — branches, remotes, fork vs clone, fetch vs pull all locked in.* \ No newline at end of file diff --git a/2026/day-23/git-command.md b/2026/day-23/git-command.md new file mode 100644 index 0000000000..3068c9ff4c --- /dev/null +++ b/2026/day-23/git-command.md @@ -0,0 +1,104 @@ +# Git Commands Reference + +> A living document of Git commands — updated daily as I learn more. +> Started: Day 22 | Last Updated: Day 23 + +--- + +## Setup & Config + +| Command | What It Does | Example | +|--------|--------------|---------| +| `git --version` | Checks the installed Git version | `git --version` | +| `git config --global user.name` | Sets your global Git username | `git config --global user.name "Jane Dev"` | +| `git config --global user.email` | Sets your global Git email | `git config --global user.email "jane@example.com"` | +| `git config --list` | Lists all Git configuration settings | `git config --list` | +| `git config --global core.editor` | Sets the default editor for commit messages | `git config --global core.editor "vim"` | + +--- + +## Repository Setup + +| Command | What It Does | Example | +|--------|--------------|---------| +| `git init` | Initializes a new Git repository in the current folder | `git init` | +| `git clone ` | Copies a remote repository to your local machine | `git clone https://github.com/user/repo.git` | + +--- + +## Basic Workflow + +| Command | What It Does | Example | +|--------|--------------|---------| +| `git status` | Shows the state of working directory and staging area | `git status` | +| `git add ` | Stages a specific file for the next commit | `git add git-commands.md` | +| `git add .` | Stages all changed files in the current directory | `git add .` | +| `git commit -m` | Records staged changes with a message | `git commit -m "Add git commands reference"` | +| `git commit --amend` | Modifies the most recent commit | `git commit --amend -m "Better message"` | + +--- + +## Viewing Changes + +| Command | What It Does | Example | +|--------|--------------|---------| +| `git log` | Shows the full commit history with details | `git log` | +| `git log --oneline` | Shows compact one-line commit history | `git log --oneline` | +| `git log --oneline --graph` | Shows history as an ASCII branch graph | `git log --oneline --graph --all` | +| `git diff` | Shows unstaged changes since the last commit | `git diff` | +| `git diff --staged` | Shows changes that are staged for commit | `git diff --staged` | +| `git show ` | Shows details and changes of a specific commit | `git show a1b2c3d` | + +--- + +## Undoing Changes + +| Command | What It Does | Example | +|--------|--------------|---------| +| `git restore ` | Discards unstaged changes in a file | `git restore notes.md` | +| `git restore --staged ` | Unstages a file (keeps changes in working dir) | `git restore --staged notes.md` | +| `git revert ` | Creates a new commit that undoes a previous commit | `git revert a1b2c3d` | + +--- + +## Branching + +| Command | What It Does | Example | +|--------|--------------|---------| +| `git branch` | Lists all local branches; asterisk marks current | `git branch` | +| `git branch -a` | Lists local and remote-tracking branches | `git branch -a` | +| `git branch ` | Creates a new branch (stays on current branch) | `git branch feature-1` | +| `git switch ` | Switches to an existing branch | `git switch feature-1` | +| `git switch -c ` | Creates a new branch and switches to it in one step | `git switch -c feature-2` | +| `git checkout -b ` | Older equivalent of `git switch -c` | `git checkout -b feature-2` | +| `git branch -d ` | Safely deletes a branch (refuses if unmerged) | `git branch -d feature-2` | +| `git branch -D ` | Force-deletes a branch regardless of merge status | `git branch -D feature-2` | +| `git merge ` | Merges the named branch into the current branch | `git merge feature-1` | + +--- + +## Remote & GitHub + +| Command | What It Does | Example | +|--------|--------------|---------| +| `git remote add ` | Connects your local repo to a remote | `git remote add origin https://github.com/user/repo.git` | +| `git remote -v` | Lists all configured remotes and their URLs | `git remote -v` | +| `git remote remove ` | Removes a remote connection | `git remote remove upstream` | +| `git push -u origin ` | Pushes a branch to remote and sets upstream tracking | `git push -u origin main` | +| `git push` | Pushes current branch to its tracked remote branch | `git push` | +| `git fetch` | Downloads changes from remote without merging | `git fetch origin` | +| `git pull` | Fetches and merges remote changes into current branch | `git pull origin main` | + +--- + +## Exploring the Repository + +| Command | What It Does | Example | +|--------|--------------|---------| +| `ls -la .git/` | Lists the contents of the hidden .git directory | `ls -la .git/` | +| `cat .git/HEAD` | Shows which branch/commit HEAD currently points to | `cat .git/HEAD` | +| `cat .git/config` | Shows repository-level Git config | `cat .git/config` | + +--- + +*More commands will be added in upcoming days as new topics are covered.* \ No newline at end of file diff --git a/2026/day-24/day-24-notes.md b/2026/day-24/day-24-notes.md new file mode 100644 index 0000000000..47f98d19de --- /dev/null +++ b/2026/day-24/day-24-notes.md @@ -0,0 +1,377 @@ +# Day 24 – Advanced Git: Merge, Rebase, Stash & Cherry-Pick + +--- + +## Task 1: Git Merge + +### Hands-On Walkthrough + +#### Fast-forward merge (`feature-login`) + +```bash +# Start from main, create feature-login +git switch -c feature-login + +# Add commits (main has NOT moved since we branched) +echo "login form html" >> login.md && git add . && git commit -m "feat: add login form" +echo "login validation" >> login.md && git add . && git commit -m "feat: add login validation" + +# Switch back to main and merge +git switch main +git merge feature-login +# Output: Updating a1c88f0..7d2e04a +# Fast-forward +``` + +Because `main` had no new commits since `feature-login` was created, Git simply moved the `main` pointer forward. No merge commit was created. + +``` +Before: main + ↓ + A ── B ── C + \ + D ── E ← feature-login + +After fast-forward: + A ── B ── C ── D ── E + ↑ + main (moved forward) +``` + +--- + +#### Merge commit (`feature-signup`) + +```bash +git switch -c feature-signup +echo "signup form" >> signup.md && git add . && git commit -m "feat: add signup form" + +# Add a commit to main BEFORE merging — this is the key difference +git switch main +echo "readme update" >> README.md && git add . && git commit -m "docs: update readme" + +# Now merge — branches have diverged +git merge feature-signup +# Git opens editor for merge commit message +# Output: Merge made by the 'ort' strategy +``` + +``` +Before: main + ↓ + A ── B ── C ── M1 ← (new commit on main) + \ + D ── E ← feature-signup + +After merge commit: + A ── B ── C ── M1 ── ● ← merge commit (main) + \ / + D ── E +``` + +--- + +### Intentional Merge Conflict + +```bash +git switch -c feature-conflict +# Edit line 1 of config.md on this branch +echo "timeout=60" > config.md && git add . && git commit -m "set timeout to 60" + +git switch main +# Edit the SAME line 1 of config.md on main +echo "timeout=30" > config.md && git add . && git commit -m "set timeout to 30" + +git merge feature-conflict +# CONFLICT (content): Merge conflict in config.md +# Automatic merge failed; fix conflicts and then commit the result. +``` + +The file now contains conflict markers: +``` +<<<<<<< HEAD +timeout=30 +======= +timeout=60 +>>>>>>> feature-conflict +``` + +To resolve: edit the file to keep the correct value, then: +```bash +git add config.md +git commit -m "resolve: keep timeout=60 from feature-conflict" +``` + +--- + +### Answers + +**What is a fast-forward merge?** + +A fast-forward merge happens when the branch being merged is directly ahead of the target branch — meaning the target has no new commits since the branch was created. Git doesn't need to create a merge commit; it just moves the target branch pointer forward to the tip of the feature branch. The result is a perfectly linear history with no merge commit at all. + +**When does Git create a merge commit instead?** + +Git creates a merge commit when both branches have diverged — i.e., both have commits the other doesn't have. Git finds the common ancestor commit, applies both sets of changes, and records a new commit with two parents. This preserves the full branching structure in the history. + +**What is a merge conflict?** + +A merge conflict occurs when two branches make changes to the same part of the same file and Git cannot automatically determine which version to keep. Git pauses the merge, marks the conflicting sections in the file with `<<<<<<<`, `=======`, and `>>>>>>>` markers, and waits for you to manually choose the correct content. After resolving, you stage the file and complete the merge with a commit. + +--- + +## Task 2: Git Rebase + +### Hands-On Walkthrough + +```bash +git switch main +git switch -c feature-dashboard +echo "widget 1" >> dashboard.md && git add . && git commit -m "feat: add widget 1" +echo "widget 2" >> dashboard.md && git add . && git commit -m "feat: add widget 2" +echo "widget 3" >> dashboard.md && git add . && git commit -m "feat: add widget 3" + +# Move main ahead (simulate another dev's work) +git switch main +echo "navbar update" >> navbar.md && git add . && git commit -m "feat: update navbar" + +# Rebase feature-dashboard onto the new main +git switch feature-dashboard +git rebase main +``` + +**`git log --oneline --graph --all` after rebase:** +``` +* f9a1b2c (HEAD -> feature-dashboard) feat: add widget 3 +* 8e3d4a1 feat: add widget 2 +* 2b5c6f0 feat: add widget 1 +* 7d2e04a (main) feat: update navbar +* a1c88f0 docs: update readme +* 3b6d711 Initial commit +``` + +The history is perfectly linear — no merge commit, no branch fork visible. + +**Compare with what merge would look like:** +``` +* c3f8a21 (HEAD -> feature-dashboard) Merge branch 'main' into feature-dashboard +|\ +| * 7d2e04a (main) feat: update navbar +* | f9a1b2c feat: add widget 3 +* | 8e3d4a1 feat: add widget 2 +* | 2b5c6f0 feat: add widget 1 +|/ +* a1c88f0 docs: update readme +``` + +--- + +### Answers + +**What does rebase actually do to your commits?** + +Rebase re-plays your commits on top of a new base commit. For each commit on your branch, Git: +1. Temporarily removes it (saves the diff as a patch) +2. Moves to the new base (the tip of `main`) +3. Re-applies the patch as a brand new commit + +The new commits have different SHA hashes even if the content is identical — they are literally new commits with a different parent. The old commits are abandoned and will eventually be garbage-collected. + +**How is the history different from a merge?** + +Merge preserves the true history — you can see exactly when branches diverged and converged. Rebase rewrites history to appear as though all work happened sequentially on a single line. Rebase produces a cleaner `git log`, but merge is a more truthful record of what actually happened. + +**Why should you never rebase commits that have been pushed and shared?** + +When you rebase, Git creates entirely new commits with new hashes. If collaborators have already based work on your original commits, their history and yours now disagree about what those commits are. When they try to push or pull, Git sees two divergent histories and either produces confusing conflicts or, if forced, silently discards their work. The golden rule: **never rewrite public history**. + +**When to use rebase vs merge?** + +| Situation | Use | +|-----------|-----| +| Keeping a local feature branch up to date with main | Rebase | +| Preparing clean commits before opening a PR | Rebase (interactive) | +| Merging a completed feature into main | Merge (preserves context) | +| Working on a shared branch others are using | Merge only | +| Want linear history in a solo or small team project | Rebase | + +--- + +## Task 3: Squash Commit vs Merge Commit + +### Hands-On Walkthrough + +```bash +# feature-profile: several messy commits +git switch -c feature-profile +echo "v1" >> profile.md && git add . && git commit -m "wip: start profile" +echo "v2" >> profile.md && git add . && git commit -m "fix: typo" +echo "v3" >> profile.md && git add . && git commit -m "fix: formatting" +echo "v4" >> profile.md && git add . && git commit -m "wip: almost done" +echo "v5" >> profile.md && git add . && git commit -m "feat: profile complete" + +git switch main +git merge --squash feature-profile +# Stages all changes but does NOT create a commit yet +git commit -m "feat: add user profile page" + +git log --oneline +# → only ONE new commit on main despite 5 commits on the branch +``` + +```bash +# feature-settings: regular merge for comparison +git switch -c feature-settings +echo "s1" >> settings.md && git add . && git commit -m "feat: settings layout" +echo "s2" >> settings.md && git add . && git commit -m "feat: settings logic" + +git switch main +git merge feature-settings --no-ff +# → creates a merge commit; both individual commits visible in git log +``` + +--- + +### Answers + +**What does squash merging do?** + +`git merge --squash` takes all commits from the feature branch, combines their diffs into a single set of staged changes in your working directory, but does NOT create a commit. You then write one clean, meaningful commit yourself. The feature branch's individual commits never appear in `main`'s history. + +**When to use squash vs regular merge?** + +| Scenario | Use | +|----------|-----| +| Branch has messy WIP / fixup commits not worth preserving | Squash | +| Feature has well-structured, meaningful commits worth keeping | Regular merge | +| Team convention is one commit per PR | Squash | +| You want full audit trail of development steps | Regular merge | + +**Trade-off of squashing** + +You lose the granular history of how the feature was built. If a bug is introduced, `git bisect` can only narrow it to the squash commit — not the specific small commit that caused it. Squashing also makes it harder to understand the reasoning behind individual changes when reading history later. + +--- + +## Task 4: Git Stash + +### Hands-On Walkthrough + +```bash +# Make uncommitted changes +echo "work in progress" >> feature.md + +# Try to switch branches — Git warns you +git switch main +# error: Your local changes to the following files would be overwritten by checkout: +# feature.md +# Please commit or stash your changes before switching. + +# Stash the work-in-progress +git stash push -m "WIP: feature.md changes" +# Saved working directory and index state On feature-1: WIP: feature.md changes + +# Now the switch works +git switch main +# Do urgent work on main... +echo "hotfix" >> navbar.md && git add . && git commit -m "fix: urgent navbar hotfix" + +# Go back and restore stashed work +git switch feature-1 +git stash pop +# Applied and dropped stash@{0} +``` + +#### Stashing multiple times and listing + +```bash +git stash push -m "experiment A" +# make more changes +git stash push -m "experiment B" + +git stash list +# stash@{0}: On feature-1: experiment B +# stash@{1}: On feature-1: experiment A +# stash@{2}: On feature-1: WIP: feature.md changes + +# Apply a specific stash by index (does not drop it) +git stash apply stash@{1} + +# Drop a stash manually after applying +git stash drop stash@{1} + +# Or apply and drop in one step +git stash pop stash@{0} +``` + +--- + +### Answers + +**`git stash pop` vs `git stash apply`** + +| | `git stash pop` | `git stash apply` | +|---|---|---| +| Applies stash? | Yes | Yes | +| Removes from stash list? | Yes (drops it) | No (keeps it) | +| Use when | You're done with this stash | You want to apply to multiple branches or keep as backup | + +**Real-world stash scenarios** + +- A critical production bug is reported mid-feature — stash your WIP, switch to `main`, create a hotfix branch +- You started coding on the wrong branch — stash, switch to the correct branch, pop +- You want to test how the codebase behaves without your changes temporarily +- Quickly check something on another branch without making a throwaway commit + +--- + +## Task 5: Cherry-Pick + +### Hands-On Walkthrough + +```bash +git switch -c feature-hotfix +echo "change A" >> app.md && git add . && git commit -m "fix: change A" +echo "change B" >> app.md && git add . && git commit -m "fix: change B ← we want this one" +echo "change C" >> app.md && git add . && git commit -m "feat: change C" + +git log --oneline +# a3f9c21 feat: change C +# 7b2d1e0 fix: change B ← target commit hash +# 4c8a0f3 fix: change A + +git switch main +git cherry-pick 7b2d1e0 +# [main f1e2d3c] fix: change B +# 1 file changed, 1 insertion(+) + +git log --oneline +# f1e2d3c fix: change B ← only this commit, applied cleanly +# ...previous main commits +``` + +--- + +### Answers + +**What does cherry-pick do?** + +`git cherry-pick ` takes the diff introduced by a specific commit and re-applies it as a new commit on the current branch. Like rebase, it creates a new commit with a new hash — the content is the same but the parent lineage is different. It does not move or delete the original commit from its source branch. + +**When to use cherry-pick in a real project** + +- A bug fix was committed to a feature branch but needs to go to `main` immediately without merging the entire feature +- You're maintaining multiple release branches (v1.x, v2.x) and need to backport a security patch to each +- Someone accidentally committed a useful change to the wrong branch +- You want to apply a single config change from an experimental branch to production + +**What can go wrong with cherry-picking** + +- **Duplicate commits**: If you later merge the source branch, Git may not recognize the cherry-picked commit as already applied, resulting in duplicate changes (or conflicts) +- **Context loss**: A commit may depend on earlier commits that don't exist on the target branch, causing conflicts +- **Diverging history**: The same logical change now exists as two different commits with different hashes, making history harder to read +- **Over-use as a crutch**: Frequent cherry-picking is often a sign of a branching strategy that should be revisited + +--- + +*Day 24 complete — merge strategies, rebase mechanics, stash workflow, and cherry-pick all covered.* \ No newline at end of file diff --git a/2026/day-24/git-commands.md b/2026/day-24/git-commands.md new file mode 100644 index 0000000000..a50471bd8e --- /dev/null +++ b/2026/day-24/git-commands.md @@ -0,0 +1,150 @@ +# Git Commands Reference + +> A living document of Git commands — updated daily as I learn more. +> Started: Day 22 | Last Updated: Day 24 + +--- + +## Setup & Config + +| Command | What It Does | Example | +|--------|--------------|---------| +| `git --version` | Checks the installed Git version | `git --version` | +| `git config --global user.name` | Sets your global Git username | `git config --global user.name "Jane Dev"` | +| `git config --global user.email` | Sets your global Git email | `git config --global user.email "jane@example.com"` | +| `git config --list` | Lists all Git configuration settings | `git config --list` | +| `git config --global core.editor` | Sets the default editor for commit messages | `git config --global core.editor "vim"` | + +--- + +## Repository Setup + +| Command | What It Does | Example | +|--------|--------------|---------| +| `git init` | Initializes a new Git repository in the current folder | `git init` | +| `git clone ` | Copies a remote repository to your local machine | `git clone https://github.com/user/repo.git` | + +--- + +## Basic Workflow + +| Command | What It Does | Example | +|--------|--------------|---------| +| `git status` | Shows the state of working directory and staging area | `git status` | +| `git add ` | Stages a specific file for the next commit | `git add git-commands.md` | +| `git add .` | Stages all changed files in the current directory | `git add .` | +| `git commit -m` | Records staged changes with a message | `git commit -m "Add git commands reference"` | +| `git commit --amend` | Modifies the most recent commit | `git commit --amend -m "Better message"` | + +--- + +## Viewing Changes + +| Command | What It Does | Example | +|--------|--------------|---------| +| `git log` | Shows the full commit history with details | `git log` | +| `git log --oneline` | Shows compact one-line commit history | `git log --oneline` | +| `git log --oneline --graph --all` | Shows full history as ASCII branch graph across all branches | `git log --oneline --graph --all` | +| `git diff` | Shows unstaged changes since the last commit | `git diff` | +| `git diff --staged` | Shows changes that are staged for commit | `git diff --staged` | +| `git show ` | Shows details and changes of a specific commit | `git show a1b2c3d` | + +--- + +## Undoing Changes + +| Command | What It Does | Example | +|--------|--------------|---------| +| `git restore ` | Discards unstaged changes in a file | `git restore notes.md` | +| `git restore --staged ` | Unstages a file (keeps changes in working dir) | `git restore --staged notes.md` | +| `git revert ` | Creates a new commit that undoes a previous commit | `git revert a1b2c3d` | + +--- + +## Branching + +| Command | What It Does | Example | +|--------|--------------|---------| +| `git branch` | Lists all local branches; asterisk marks current | `git branch` | +| `git branch -a` | Lists local and remote-tracking branches | `git branch -a` | +| `git branch ` | Creates a new branch (stays on current branch) | `git branch feature-1` | +| `git switch ` | Switches to an existing branch | `git switch feature-1` | +| `git switch -c ` | Creates a new branch and switches to it in one step | `git switch -c feature-2` | +| `git checkout -b ` | Older equivalent of `git switch -c` | `git checkout -b feature-2` | +| `git branch -d ` | Safely deletes a branch (refuses if unmerged) | `git branch -d feature-2` | +| `git branch -D ` | Force-deletes a branch regardless of merge status | `git branch -D feature-2` | + +--- + +## Merging + +| Command | What It Does | Example | +|--------|--------------|---------| +| `git merge ` | Merges named branch into current branch | `git merge feature-login` | +| `git merge --no-ff ` | Forces a merge commit even when fast-forward is possible | `git merge --no-ff feature-login` | +| `git merge --squash ` | Combines all branch commits into one staged changeset (you commit manually) | `git merge --squash feature-profile` | +| `git merge --abort` | Cancels an in-progress merge and restores previous state | `git merge --abort` | + +--- + +## Rebasing + +| Command | What It Does | Example | +|--------|--------------|---------| +| `git rebase ` | Re-plays current branch's commits on top of named branch | `git rebase main` | +| `git rebase -i HEAD~` | Interactive rebase — squash, reorder, or edit last n commits | `git rebase -i HEAD~3` | +| `git rebase --abort` | Cancels an in-progress rebase and restores original state | `git rebase --abort` | +| `git rebase --continue` | Continues a rebase after resolving a conflict | `git rebase --continue` | + +--- + +## Stash + +| Command | What It Does | Example | +|--------|--------------|---------| +| `git stash` | Saves uncommitted changes and cleans the working directory | `git stash` | +| `git stash push -m ""` | Stashes with a descriptive label | `git stash push -m "WIP: login form"` | +| `git stash list` | Shows all saved stashes | `git stash list` | +| `git stash pop` | Applies the most recent stash and removes it from the list | `git stash pop` | +| `git stash apply stash@{n}` | Applies a specific stash without removing it | `git stash apply stash@{1}` | +| `git stash drop stash@{n}` | Deletes a specific stash from the list | `git stash drop stash@{0}` | +| `git stash clear` | Deletes all stashes | `git stash clear` | + +--- + +## Cherry-Pick + +| Command | What It Does | Example | +|--------|--------------|---------| +| `git cherry-pick ` | Applies a specific commit's changes onto the current branch | `git cherry-pick 7b2d1e0` | +| `git cherry-pick

..

` | Applies a range of commits (exclusive of h1) | `git cherry-pick a1b2c3..f4e5d6` | +| `git cherry-pick --abort` | Cancels an in-progress cherry-pick | `git cherry-pick --abort` | +| `git cherry-pick --continue` | Continues after resolving a cherry-pick conflict | `git cherry-pick --continue` | + +--- + +## Remote & GitHub + +| Command | What It Does | Example | +|--------|--------------|---------| +| `git remote add ` | Connects your local repo to a remote | `git remote add origin https://github.com/user/repo.git` | +| `git remote -v` | Lists all configured remotes and their URLs | `git remote -v` | +| `git remote remove ` | Removes a remote connection | `git remote remove upstream` | +| `git push -u origin ` | Pushes a branch to remote and sets upstream tracking | `git push -u origin main` | +| `git push` | Pushes current branch to its tracked remote branch | `git push` | +| `git fetch` | Downloads changes from remote without merging | `git fetch origin` | +| `git pull` | Fetches and merges remote changes into current branch | `git pull origin main` | + +--- + +## Exploring the Repository + +| Command | What It Does | Example | +|--------|--------------|---------| +| `ls -la .git/` | Lists the contents of the hidden .git directory | `ls -la .git/` | +| `cat .git/HEAD` | Shows which branch/commit HEAD currently points to | `cat .git/HEAD` | +| `cat .git/config` | Shows repository-level Git config | `cat .git/config` | + +--- + +*More commands will be added in upcoming days as new topics are covered.* \ No newline at end of file diff --git a/2026/day-25/day-25-notes.md b/2026/day-25/day-25-notes.md new file mode 100644 index 0000000000..21944270ca --- /dev/null +++ b/2026/day-25/day-25-notes.md @@ -0,0 +1,736 @@ +# Day 25 – Git Reset vs Revert & Branching Strategies + +## Task 1: Git Reset — Hands-On + +### Simulated Commit History +``` +git init practice-repo && cd practice-repo + +# Commit A +echo "feature A" > file.txt && git add . && git commit -m "Commit A" + +# Commit B +echo "feature B" >> file.txt && git add . && git commit -m "Commit B" + +# Commit C +echo "feature C" >> file.txt && git add . && git commit -m "Commit C" +``` + +Log before reset: +``` +* c3f1a2b (HEAD -> main) Commit C +* b2e0f1a Commit B +* a1d9e0c Commit A +``` + +--- + +### `git reset --soft HEAD~1` +```bash +git reset --soft HEAD~1 +``` +**What happens:** +- HEAD moves back to Commit B +- Changes from Commit C remain **staged** (in the index) +- Working directory is **unchanged** +- `git status` shows: "Changes to be committed" + +**Observation:** It's like un-committing but keeping everything staged — ready to re-commit immediately. + +--- + +### `git reset --mixed HEAD~1` (default) +```bash +git add . && git commit -m "Commit C (re-done)" +git reset --mixed HEAD~1 # or just: git reset HEAD~1 +``` +**What happens:** +- HEAD moves back one commit +- Changes are **unstaged** (removed from index) +- Working directory is **unchanged** +- `git status` shows: "Changes not staged for commit" + +**Observation:** Changes are back in the working directory but need `git add` before recommitting. + +--- + +### `git reset --hard HEAD~1` +```bash +git add . && git commit -m "Commit C (re-done again)" +git reset --hard HEAD~1 +``` +**What happens:** +- HEAD moves back one commit +- Staged changes are **wiped** +- Working directory changes are **wiped** +- `git status` shows: "nothing to commit, working tree clean" + +**Observation:** Commit C's changes are completely gone from both staging and working directory. + +--- + +### Answers + +**Difference between `--soft`, `--mixed`, and `--hard`:** + +| Flag | HEAD | Index (Staged) | Working Directory | +|------|------|----------------|-------------------| +| `--soft` | Moves back | Unchanged (staged) | Unchanged | +| `--mixed` | Moves back | Cleared | Unchanged | +| `--hard` | Moves back | Cleared | **Cleared** | + +**Which one is destructive and why?** +`--hard` is destructive because it permanently erases changes from both the staging area and the working directory. There is no undo unless you use `git reflog` to find the lost commit hash within the reflog's expiry window (~90 days). + +**When would you use each one?** +- `--soft` — When you want to undo a commit but keep everything staged (e.g., to squash commits or fix a commit message with more control than `git commit --amend`) +- `--mixed` — When you want to undo a commit and unstage changes so you can selectively re-stage them (default behaviour, most common) +- `--hard` — When you want to completely discard recent commits and all their changes (e.g., throw away a bad experiment) + +**Should you ever use `git reset` on commits that are already pushed?** +**No — avoid it on shared/public branches.** When you reset and force-push (`git push --force`), you rewrite history that others have already pulled. This causes diverged histories and forces teammates to reconcile their local branches manually. It can lead to lost work and confusion. Use `git revert` instead for pushed commits. + +> **Safety net:** `git reflog` records every HEAD movement. Even after a `--hard` reset, you can recover lost commits with: +> ```bash +> git reflog +> git checkout -b recovery-branch +> ``` + +--- + +## Task 2: Git Revert — Hands-On + +### Simulated Commits +```bash +echo "X" > file.txt && git add . && git commit -m "Commit X" +echo "Y" >> file.txt && git add . && git commit -m "Commit Y" +echo "Z" >> file.txt && git add . && git commit -m "Commit Z" +``` + +Log: +``` +* 9z8y7x6 (HEAD -> main) Commit Z +* 5y4x3w2 Commit Y +* 1a2b3c4 Commit X +``` + +### Reverting the Middle Commit (Y) +```bash +git revert 5y4x3w2 +``` +Git opens an editor with a default message: `Revert "Commit Y"`. After saving: + +**What happens:** +- A **new commit** is created that undoes the changes introduced by Commit Y +- Commit Y is **still in the history** +- The file no longer contains line "Y", but history is intact + +### `git log` after revert: +``` +* d1e2f3a (HEAD -> main) Revert "Commit Y" +* 9z8y7x6 Commit Z +* 5y4x3w2 Commit Y ← still here! +* 1a2b3c4 Commit X +``` + +**Is Commit Y still in history?** ✅ Yes. Revert does not remove commits; it adds a new one. + +--- + +### Answers + +**How is `git revert` different from `git reset`?** +- `git reset` moves the HEAD pointer backward, effectively removing commits from history (rewrites history) +- `git revert` adds a new commit that applies the inverse of a previous commit — history is preserved, and the undo is itself recorded as a commit + +**Why is revert considered safer than reset for shared branches?** +Because it **doesn't rewrite history**. Everyone who has pulled the branch still has a valid, linear history. The revert commit simply adds a new change on top — no force push required, no diverged histories, no risk of overwriting teammates' work. + +**When would you use revert vs reset?** + +| Situation | Use | +|-----------|-----| +| Undo a pushed commit on a shared branch | `git revert` | +| Undo a local-only commit before pushing | `git reset` | +| Quickly discard experimental local work | `git reset --hard` | +| Undo a specific old commit in the middle of history | `git revert ` | +| Squash/clean up local commits before PR | `git reset --soft` | + +--- + +## Task 3: Reset vs Revert — Summary + +| | `git reset` | `git revert` | +|---|---|---| +| **What it does** | Moves HEAD backward, optionally discarding staged/working changes | Creates a new commit that undoes the changes of a specified commit | +| **Removes commit from history?** | ✅ Yes (rewrites history) | ❌ No (preserves history, adds new commit) | +| **Safe for shared/pushed branches?** | ❌ No — requires force push, causes diverged history for others | ✅ Yes — non-destructive, safe to push normally | +| **When to use** | Local cleanup before pushing; discarding experimental work | Undoing pushed commits; undoing specific historical changes on shared branches | + +--- + +## Task 4: Branching Strategies + +--- + +### 1. GitFlow + +**How it works:** +GitFlow defines a strict branching model with multiple long-lived branches and dedicated roles for each. + +- `main` — production-ready code only +- `develop` — integration branch; all features merge here +- `feature/*` — one branch per feature, branched from `develop` +- `release/*` — branched from `develop` when ready to prep a release; only bugfixes allowed +- `hotfix/*` — branched from `main` to quickly patch production; merged back to both `main` and `develop` + +**Text Diagram:** +``` +main ────●────────────────────────●──────────●──── + \ /↑hotfix / +develop ──────●──────────●──────────●──────────●──── + \ /↑feature \ /↑release +feature ──────────── ────────── +``` + +**When/where it's used:** +- Software with versioned releases (e.g., mobile apps, desktop software, libraries) +- Teams with formal QA and staging environments +- Projects shipping discrete v1.0, v2.0 releases + +**Pros:** +- Very structured and predictable +- Clear separation between production, staging, and active dev +- Good for parallel release management + +**Cons:** +- Complex — many branches to manage +- Slow; merges can be frequent and messy +- Overkill for small teams or continuous deployment + +--- + +### 2. GitHub Flow + +**How it works:** +Simple, lightweight. Only one long-lived branch (`main`) plus short-lived feature branches. Deploy directly from `main`. + +1. Branch off `main` with a descriptive name +2. Commit changes to the branch +3. Open a Pull Request +4. Review and discuss +5. Merge to `main` → deploy immediately + +**Text Diagram:** +``` +main ──────●────────────────────●───────────────●──── + \ /↑PR merge /↑PR merge +feature-auth ──●──●──●────────── / +fix-login ──●──●────────── +``` + +**When/where it's used:** +- Web apps and SaaS products with CI/CD pipelines +- Startups and small-to-medium teams +- Projects that deploy continuously (multiple times a day) +- GitHub itself uses this model + +**Pros:** +- Simple and easy to understand +- Fast — shorter feedback cycles +- Encourages small, frequent PRs +- Works great with CI/CD automation + +**Cons:** +- No built-in release management +- Requires solid CI/CD and automated testing to stay stable +- Less structured for managing multiple simultaneous versions + +--- + +### 3. Trunk-Based Development (TBD) + +**How it works:** +All developers commit directly to `main` (the "trunk") or use very short-lived feature branches (lifespan < 1–2 days). Feature flags are used to hide incomplete features in production. + +1. Pull latest `main` +2. Make a small, complete change +3. Push directly to `main` (or open a short-lived PR) +4. CI runs; if green, changes are live +5. Larger incomplete features are hidden behind feature flags + +**Text Diagram:** +``` +main ──●──●──●──●──●──●──●──●──●──●──●── + ↑ ↑ ↑ ↑ ↑ ↑ ↑ + Dev A B A C B A (all committing to trunk) +``` + +**When/where it's used:** +- Elite engineering teams (Google, Facebook, Netflix) +- Projects with mature CI/CD pipelines and high test coverage +- Teams practising continuous delivery / continuous deployment +- Google has used TBD across its monorepo for years + +**Pros:** +- Eliminates merge hell — no long-lived branches diverging +- Forces small, incremental commits (better code quality) +- Fastest possible deployment cycle +- Naturally encourages feature flags and incremental delivery + +**Cons:** +- Requires high discipline and test coverage +- Feature flags add complexity +- Hard to adopt on teams without CI/CD maturity +- Mistakes can reach production quickly if pipelines aren't solid + +--- + +### Strategy Recommendations + +**Which strategy for a startup shipping fast?** +**GitHub Flow.** It's simple, encourages continuous deployment, and doesn't impose overhead. Startups need to move fast and iterate — GitHub Flow lets teams ship multiple times a day with minimal ceremony. Add a CI/CD pipeline and it works beautifully. + +**Which strategy for a large team with scheduled releases?** +**GitFlow.** Large teams often have formal QA cycles, staged rollouts, and the need to maintain multiple active versions simultaneously. GitFlow's structured branches (develop, release, hotfix) map well to this kind of workflow. + +**Which one does a popular open-source project use?** +Checking the **React** repository on GitHub (github.com/facebook/react): +React uses a **GitHub Flow-inspired** model. They have a `main` branch, feature branches, and PRs. Release branches exist (e.g., `0.14-stable`) for maintaining older versions, which adds a slight GitFlow flavour for long-term support — but day-to-day development follows GitHub Flow's simple branch → PR → merge pattern. + +The **Kubernetes** project uses a more sophisticated variant closer to **GitFlow**, with `main`, `release-x.y` branches, and a formal release cycle managed by release teams. + +--- + +## Summary & Key Takeaways + +1. **`git reset`** rewrites history and should only be used on local, unpushed commits. It's powerful but dangerous on shared branches. + +2. **`git revert`** is always safe for shared branches because it adds a new commit rather than removing history. + +3. **`git reflog`** is your safety net — it tracks every movement of HEAD, letting you recover from even a `--hard` reset. + +4. **Branching strategy depends on team size and deployment model:** + - Startup / fast CI-CD → **GitHub Flow** + - Large team / scheduled releases → **GitFlow** + - Elite team / maximum velocity → **Trunk-Based Development** + + + # Git Commands Reference — Days 22–25 +> A comprehensive reference covering setup, daily workflow, branching, remotes, merging, stashing, and undoing changes. + +--- + +## 1. Setup & Config + +```bash +# Set your identity +git config --global user.name "Your Name" +git config --global user.email "you@example.com" + +# Set default editor +git config --global core.editor "code --wait" # VS Code +git config --global core.editor "vim" # Vim + +# Set default branch name +git config --global init.defaultBranch main + +# View all config +git config --list + +# View a specific setting +git config user.email + +# Store credentials (avoid re-typing password) +git config --global credential.helper store + +# Initialize a new repo +git init + +# Clone an existing repo +git clone +git clone # Clone into a specific folder +git clone --depth 1 # Shallow clone (latest snapshot only) +``` + +--- + +## 2. Basic Workflow + +### Staging & Committing + +```bash +# Check status of working tree +git status +git status -s # Short/compact format + +# Stage files +git add # Stage a specific file +git add . # Stage everything in current directory +git add -p # Interactively stage hunks (partial staging) + +# Unstage a file (keeps changes in working dir) +git restore --staged + +# Commit +git commit -m "Your message" +git commit -am "Message" # Stage tracked files + commit in one step +git commit --amend # Edit the last commit (message or content) +git commit --amend --no-edit # Amend last commit without changing message + +# Discard changes in working directory (destructive!) +git restore +git checkout -- # Older syntax, same effect +``` + +### Viewing History & Diffs + +```bash +# Log +git log +git log --oneline # Compact one-line format +git log --oneline --graph --all # Visual branch graph +git log -n 5 # Last 5 commits +git log --author="Name" +git log --since="2 weeks ago" +git log --follow # Track renames + +# Diff +git diff # Unstaged changes vs last commit +git diff --staged # Staged changes vs last commit +git diff # Diff between branches +git diff # Diff between two commits + +# Show a specific commit +git show +git show HEAD # Show latest commit +``` + +--- + +## 3. Branching + +```bash +# List branches +git branch # Local branches +git branch -a # All branches (local + remote) +git branch -v # With last commit info + +# Create a branch +git branch +git checkout -b # Create + switch (classic) +git switch -c # Create + switch (modern) + +# Switch branches +git checkout +git switch # Modern syntax + +# Rename a branch +git branch -m +git branch -m # Rename current branch + +# Delete a branch +git branch -d # Safe delete (merged only) +git branch -D # Force delete (unmerged) + +# Delete a remote-tracking branch +git branch -dr origin/ +``` + +--- + +## 4. Remote + +```bash +# View remotes +git remote -v + +# Add a remote +git remote add origin +git remote add upstream # For forks: add original repo + +# Rename / remove a remote +git remote rename origin newname +git remote remove + +# Fetch (download without merging) +git fetch origin +git fetch --all # Fetch all remotes + +# Pull (fetch + merge) +git pull +git pull origin main +git pull --rebase origin main # Pull with rebase instead of merge + +# Push +git push origin +git push -u origin # Set upstream tracking +git push --force-with-lease # Safer force push (checks remote state) +git push --force # Dangerous: overwrites remote history + +# Push tags +git push origin --tags + +# Forking workflow +# 1. Fork on GitHub +# 2. Clone your fork: git clone +# 3. Add upstream: git remote add upstream +# 4. Keep in sync: +git fetch upstream +git merge upstream/main +``` + +--- + +## 5. Merging & Rebasing + +### Merging + +```bash +# Fast-forward merge (linear history) +git merge + +# No fast-forward (always creates a merge commit) +git merge --no-ff + +# Abort an in-progress merge +git merge --abort + +# After resolving conflicts manually: +git add +git merge --continue + +# Squash all commits from branch into one staged change +git merge --squash +``` + +### Rebasing + +```bash +# Rebase current branch onto main +git rebase main + +# Interactive rebase (last N commits) +git rebase -i HEAD~3 # Opens editor to squash/reorder/edit + +# Interactive rebase options: +# pick = keep commit as-is +# reword = keep commit, edit message +# squash = combine with previous commit +# fixup = combine, discard this message +# drop = remove commit entirely + +# Abort a rebase +git rebase --abort + +# Continue after resolving conflicts +git rebase --continue +``` + +**Merge vs Rebase:** +| | Merge | Rebase | +|---|---|---| +| History | Preserves branch topology | Creates linear history | +| Shared branches | ✅ Safe | ❌ Don't rebase public branches | +| PR cleanup | `--squash` | `--interactive` | + +--- + +## 6. Stash & Cherry-Pick + +### Stash + +```bash +# Save current changes to stash +git stash +git stash push -m "WIP: my feature" # With a label + +# List stashes +git stash list + +# Apply most recent stash (keeps stash) +git stash apply + +# Apply and remove stash +git stash pop + +# Apply a specific stash +git stash apply stash@{2} + +# Drop a specific stash +git stash drop stash@{1} + +# Clear all stashes +git stash clear + +# Stash including untracked files +git stash -u +``` + +### Cherry-Pick + +```bash +# Apply a specific commit to current branch +git cherry-pick + +# Cherry-pick a range of commits +git cherry-pick ^.. # Inclusive range + +# Cherry-pick without auto-committing +git cherry-pick -n + +# Abort cherry-pick +git cherry-pick --abort + +# Continue after resolving conflicts +git cherry-pick --continue +``` + +--- + +## 7. Reset & Revert + +### Understanding the Three Trees +Git manages three areas: +- **HEAD** — the last commit snapshot +- **Index (Staging Area)** — what will go into the next commit +- **Working Directory** — actual files on disk + +### Git Reset + +```bash +# Soft reset — moves HEAD, keeps index staged +git reset --soft HEAD~1 +git reset --soft + +# Mixed reset (default) — moves HEAD, clears index, keeps working dir +git reset HEAD~1 +git reset --mixed HEAD~1 +git reset --mixed + +# Hard reset — moves HEAD, clears index AND working directory ⚠️ DESTRUCTIVE +git reset --hard HEAD~1 +git reset --hard + +# Unstage a file (non-destructive) +git reset HEAD +git restore --staged # Modern syntax +``` + +**Reset Behaviour Summary:** + +| Flag | HEAD | Index | Working Dir | Destructive? | +|------|------|-------|-------------|--------------| +| `--soft` | ✅ Moves | Unchanged | Unchanged | No | +| `--mixed` | ✅ Moves | ✅ Cleared | Unchanged | No | +| `--hard` | ✅ Moves | ✅ Cleared | ✅ Cleared | **Yes** | + +> ⚠️ **Never reset commits that have been pushed to a shared branch.** Use `git revert` instead. + +### Git Revert + +```bash +# Revert a specific commit (creates a new "undo" commit) +git revert + +# Revert without opening editor +git revert --no-edit + +# Revert a range of commits +git revert .. + +# Stage the revert without committing (then commit manually) +git revert -n + +# Abort an in-progress revert +git revert --abort +``` + +### Reset vs Revert Comparison + +| | `git reset` | `git revert` | +|---|---|---| +| What it does | Moves HEAD backward, optionally discards changes | Creates a new commit undoing specified changes | +| Rewrites history? | ✅ Yes | ❌ No | +| Safe for pushed branches? | ❌ No | ✅ Yes | +| Use case | Local cleanup, discarding unpushed work | Undoing changes on shared/remote branches | + +### Reflog — Your Safety Net + +```bash +# View full history of HEAD movements (including resets!) +git reflog + +# Recover a lost commit after hard reset +git reflog # Find the hash +git checkout -b recovery # Recover to a new branch +git reset --hard # Or reset current branch back + +# Reflog entries expire after ~90 days by default +``` + +--- + +## 8. Tags + +```bash +# Lightweight tag +git tag v1.0 + +# Annotated tag (recommended for releases) +git tag -a v1.0 -m "Version 1.0 release" + +# Tag a past commit +git tag -a v0.9 + +# List tags +git tag +git tag -l "v1.*" # Filter by pattern + +# Push a tag +git push origin v1.0 +git push origin --tags # Push all tags + +# Delete a tag +git tag -d v1.0 # Local +git push origin --delete v1.0 # Remote +``` + +--- + +## 9. Useful Utilities + +```bash +# Find which commit introduced a bug (binary search) +git bisect start +git bisect bad # Current commit is bad +git bisect good # Last known good commit +# Git checks out midpoint; test and mark: +git bisect good / git bisect bad +git bisect reset # When done + +# See who last modified each line of a file +git blame +git blame -L 10,20 # Specific line range + +# Search commit messages +git log --grep="bug fix" + +# Search code changes +git log -S "function_name" # Pickaxe search + +# Clean untracked files +git clean -n # Dry run (show what would be deleted) +git clean -f # Delete untracked files +git clean -fd # Delete untracked files and directories +``` + +--- + +## Branching Strategy Quick Reference + +| Strategy | Best For | Key Branches | Deploy From | +|---|---|---|---| +| **GitHub Flow** | Startups, CI/CD, continuous deploy | `main` + feature branches | `main` | +| **GitFlow** | Scheduled releases, large teams | `main`, `develop`, `feature/*`, `release/*`, `hotfix/*` | `main` | +| **Trunk-Based** | Elite teams, maximum velocity | `main` (short-lived feature branches optional) | `main` | \ No newline at end of file diff --git a/2026/day-29/day-29-docker-basics.md b/2026/day-29/day-29-docker-basics.md new file mode 100644 index 0000000000..186eec8e5a --- /dev/null +++ b/2026/day-29/day-29-docker-basics.md @@ -0,0 +1,150 @@ +90 Days of DevOps +Day 29 +Introduction to Docker +Containers, Architecture & First Deployments +#DevOpsKaJosh | #TrainWithShubham +Task 1: What is Docker? + +What is a Container? +A container is a lightweight, standalone, executable package that includes everything needed to run a piece of software: the code, runtime, system tools, libraries, and settings. Containers isolate software from its environment and ensure it works uniformly across different stages of deployment. + +Why do we need containers? +• Eliminate the "it works on my machine" problem +• Pack dependencies alongside the app — no version conflicts +• Spin up or tear down environments in seconds +• Run dozens of isolated apps on one host without full OS overhead +• Enable consistent CI/CD pipelines from dev to production + +Containers vs Virtual Machines +Feature Container Virtual Machine +OS Shares host OS kernel Full guest OS per VM +Startup time Milliseconds Minutes +Size Megabytes Gigabytes +Isolation Process-level Hardware-level (hypervisor) +Performance Near-native Slight overhead +Portability High — runs anywhere Docker runs Lower — image tied to hypervisor +Use case Microservices, CI/CD, cloud-native Full OS isolation, legacy apps + +Docker Architecture +Docker uses a client-server architecture. Here is how each component fits together: + +• Docker Client — The CLI tool you interact with (docker run, docker ps, etc.). Sends commands to the Docker daemon via REST API. +• Docker Daemon (dockerd) — The background service that actually manages images, containers, networks, and volumes. Listens for API requests. +• Docker Images — Read-only templates used to create containers. Built using a Dockerfile and stored locally or in a registry. +• Docker Containers — Running instances of images. Each container is isolated with its own filesystem, networking, and process space. +• Docker Registry — A storage and distribution system for images. Docker Hub is the default public registry. Private registries (ECR, GCR, Harbor) are also common. + +Flow: You (Docker Client) → docker run nginx → Docker Daemon → checks local images → pulls from Docker Hub → creates & starts Container + +Task 2: Install Docker + +Installation Steps +1. Update package index and install prerequisites +sudo apt-get update +sudo apt-get install ca-certificates curl gnupg + +2. Add Docker's official GPG key and repository +sudo install -m 0755 -d /etc/apt/keyrings +curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpg +echo "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null + +3. Install Docker Engine +sudo apt-get update +sudo apt-get install docker-ce docker-ce-cli containerd.io docker-compose-plugin + +4. Verify the installation +docker --version +docker info + +Run Hello World Container +docker run hello-world + +What happens under the hood when you run this command: +• Docker Client sends the request to Docker Daemon +• Daemon checks if the hello-world image exists locally — it doesn't +• Daemon pulls hello-world from Docker Hub (public registry) +• Daemon creates a container from the image +• Container runs, prints the welcome message, then exits + +Task 3: Run Real Containers + +1. Run Nginx Web Server +docker run -d -p 8080:80 --name my-nginx nginx +Open your browser and navigate to http://localhost:8080 — you should see the Nginx welcome page. + +2. Run Ubuntu in Interactive Mode +docker run -it --name ubuntu-explore ubuntu bash +You are now inside a full Ubuntu container. Explore it like a mini Linux machine: +cat /etc/os-release # Check the OS version +ls / # Browse the filesystem +apt-get update # Update package lists +exit # Leave the container + +3. List Running Containers +docker ps + +4. List ALL Containers (including stopped) +docker ps -a + +5. Stop and Remove a Container +docker stop my-nginx +docker rm my-nginx + +Task 4: Explore Docker Features + +1. Detached Mode +Detached mode (-d) runs the container in the background. Your terminal is immediately freed up — you don't see live output. The container keeps running even after you close the terminal session. +docker run -d nginx + +2. Custom Container Name +docker run -d --name webserver nginx +Naming containers makes them easier to reference instead of using long container IDs. + +3. Port Mapping +Format: -p : +docker run -d -p 9090:80 --name port-demo nginx +Container port 80 (Nginx inside) is mapped to host port 9090. Access it at http://localhost:9090. + +4. Check Logs +docker logs webserver +docker logs -f webserver # Follow / stream live logs + +5. Execute a Command Inside a Running Container +docker exec -it webserver bash +docker exec webserver ls /etc/nginx # Run a single command + +Docker Command Quick Reference + +Command Description +docker run Create and start a container from an image +docker run -d Run container in detached (background) mode +docker run -it Run container in interactive mode with terminal +docker run -p h:c Map host port h to container port c +docker run --name Assign a custom name to the container +docker ps List currently running containers +docker ps -a List all containers (running + stopped) +docker stop Gracefully stop a running container +docker rm Remove a stopped container +docker logs View output logs of a container +docker logs -f Stream/follow logs in real time +docker exec -it Open interactive shell inside running container +docker images List locally available images +docker pull Download image from registry without running +docker rmi Remove a local image + +Why This Matters for DevOps + +Docker is the foundation of modern software deployment. Here is why every DevOps engineer must know it: + +• CI/CD Pipelines — Every pipeline stage (build, test, deploy) runs inside containers for consistency +• Kubernetes — K8s orchestrates Docker containers at scale; you cannot use K8s without understanding Docker +• Microservices — Each service runs in its own container, independently deployable and scalable +• Environment Parity — Dev, staging, and prod environments are identical because they use the same image +• Infrastructure as Code — Dockerfiles define infrastructure declaratively, version-controlled alongside code + +Today's Key Takeaway +Containers package your app and its dependencies into a portable, isolated unit. Docker makes creating, running, and managing containers simple. Every modern deployment — from a startup to Netflix — relies on this technology. + +Day 29 Complete +#90DaysOfDevOps | #DevOpsKaJosh | #TrainWithShubham +Happy Learning! — TrainWithShubham diff --git a/2026/day-31/day-31-dockerfile.md b/2026/day-31/day-31-dockerfile.md new file mode 100644 index 0000000000..ca16451705 --- /dev/null +++ b/2026/day-31/day-31-dockerfile.md @@ -0,0 +1,292 @@ +90 Days of DevOps +Day 31 +Dockerfile: Build Your Own Images +Write Dockerfiles. Build custom images. Ship software. +#DevOpsKaJosh | #TrainWithShubham +Overview + +A Dockerfile is a text file containing instructions to build a Docker image. Every instruction creates a new layer in the image. Understanding Dockerfiles is the key difference between someone who uses Docker and someone who actually ships software with Docker. + +Today's Learning Goal +Write Dockerfiles from scratch, understand every core instruction, grasp the difference between CMD and ENTRYPOINT, build a real web app image, and learn cache-aware layer optimization. + +Task 1: Your First Dockerfile + +Project Structure +my-first-image/ +└── Dockerfile + +Dockerfile +# my-first-image/Dockerfile +FROM ubuntu:22.04 + +RUN apt-get update && apt-get install -y curl \ + && rm -rf /var/lib/apt/lists/* + +CMD ["echo", "Hello from my custom image!"] + +Build and Run +# Build and tag the image +docker build -t my-ubuntu:v1 . + +# Run a container from your new image +docker run my-ubuntu:v1 + +# Expected output: +# Hello from my custom image! + +What just happened? +Docker read each instruction top-to-bottom. FROM pulled ubuntu:22.04 as the base layer. RUN executed apt-get inside a temporary container and committed the result as a new layer. CMD stored the default command metadata — it runs when you do docker run. + +Task 2: Dockerfile Instructions + +A Dockerfile Using Every Core Instruction +# Task2/Dockerfile +FROM node:20-alpine + +# Set the working directory inside the container +WORKDIR /app + +# Copy package files first (cache-friendly — see Task 6) +COPY package*.json ./ + +# Install dependencies +RUN npm install --production + +# Copy the rest of the application code +COPY . . + +# Document that the app listens on port 3000 +EXPOSE 3000 + +# Default command to start the app +CMD ["node", "server.js"] + +What Each Instruction Does +Instruction Purpose +FROM node:20-alpine Sets the base image. Every Dockerfile must start with FROM. Alpine variants are smaller (~5 MB vs ~900 MB). +WORKDIR /app Creates the directory if needed and sets it as the current directory for all subsequent instructions. +COPY package*.json ./ Copies files from the build context (your machine) into the image at the WORKDIR path. +RUN npm install Executes a shell command during the build. Creates a new image layer with the results. +COPY . . Copies the rest of the source code. Placed after RUN npm install to maximize cache hits. +EXPOSE 3000 Documents the intended port. Does NOT actually publish the port — that requires -p at runtime. +CMD ["node", "server.js"] Sets the default command when the container starts. Can be overridden at docker run. + +Task 3: CMD vs ENTRYPOINT + +CMD — Overridable Default +# cmd-demo/Dockerfile +FROM alpine +CMD ["echo", "hello"] + +docker build -t cmd-demo . + +docker run cmd-demo +# Output: hello + +docker run cmd-demo echo goodbye +# Output: goodbye (CMD was replaced entirely) + +ENTRYPOINT — Fixed Executable +# ep-demo/Dockerfile +FROM alpine +ENTRYPOINT ["echo"] + +docker build -t ep-demo . + +docker run ep-demo +# Output: (empty line — echo with no args) + +docker run ep-demo hello devops world +# Output: hello devops world (args appended to ENTRYPOINT) + +CMD + ENTRYPOINT Together +FROM alpine +ENTRYPOINT ["echo"] +CMD ["default message"] + +# docker run → Output: default message +# docker run my-img custom msg → Output: custom msg + +When to Use Each +Use Case Instruction +Container is a utility/tool (curl, aws-cli) ENTRYPOINT — lock in the executable, pass args at runtime +Container runs a service (web app, API) CMD — define default start command, easy to override for debugging +Want a default arg but allow override ENTRYPOINT + CMD together: ENTRYPOINT is the binary, CMD is the default flag/arg +Simple scripting or ad-hoc commands CMD — most flexible for dev and experimentation + +Task 4: Build a Simple Web App Image + +Project Files +Create two files in a folder called my-website/: + +index.html + + + + + My Docker Site + + + +
+

Hello from Docker!

+

Day 31 — Served by Nginx inside a container.

+
+ + + +Dockerfile +FROM nginx:alpine + +# Remove default Nginx welcome page +RUN rm -rf /usr/share/nginx/html/* + +# Copy our HTML into the Nginx web root +COPY index.html /usr/share/nginx/html/index.html + +EXPOSE 80 + +Build and Run +docker build -t my-website:v1 . + +docker run -d -p 8080:80 --name my-site my-website:v1 + +# Visit http://localhost:8080 in your browser + +Why nginx:alpine? +The full nginx image is ~140 MB. The alpine variant is only ~23 MB — over 6x smaller. For a static site, you get identical functionality with a fraction of the storage and pull time. Always prefer alpine base images in production. + +Task 5: .dockerignore + +A .dockerignore file tells Docker which files to exclude from the build context. The build context is everything in the current directory that gets sent to the Docker daemon — even files you never COPY. A large context means slower builds. + +.dockerignore File +# .dockerignore + +# Node dependencies (rebuilt inside container) +node_modules + +# Version control +.git +.gitignore + +# Documentation (not needed in image) +*.md +README* + +# Secrets — never bake into images! +.env +*.env.* + +# Build artifacts and test files +dist/ +coverage/ +*.test.js + +Verify Ignored Files Are Excluded +# Add a test file that should be ignored +echo 'secret' > .env +echo 'big data' > README.md + +# Build and check the image filesystem +docker build -t ignore-test . +docker run --rm ignore-test ls -la /app + +# .env and README.md should NOT appear + +Security Rule +Never COPY . . without a .dockerignore. You risk baking .env secrets, AWS credentials, or SSH keys into your image. Once pushed to a registry, those secrets are exposed. Always add .dockerignore before your first COPY. + +Task 6: Build Optimization & Layer Caching + +How Docker Layer Caching Works +Each Dockerfile instruction creates an immutable layer. When you rebuild, Docker checks if the instruction and its inputs have changed. If nothing changed, Docker reuses the cached layer — skipping the work entirely. Once a layer is invalidated (changed), ALL subsequent layers are rebuilt too. + +Bad Layer Order — Slow Rebuilds +# SLOW: source code copied before installing deps +FROM node:20-alpine +WORKDIR /app +COPY . . +RUN npm install +CMD ["node", "server.js"] + +Problem: Every time you change any source file, Docker invalidates the COPY . . layer — and then re-runs npm install from scratch, even though your package.json did not change. That npm install could take 60+ seconds on every build. + +Optimized Layer Order — Fast Rebuilds +# FAST: deps installed before copying all source code +FROM node:20-alpine +WORKDIR /app + +# 1. Copy only dependency manifests (rarely change) +COPY package*.json ./ + +# 2. Install dependencies (cached until package.json changes) +RUN npm install --production + +# 3. Copy source code last (changes on every edit — no cache loss above) +COPY . . + +CMD ["node", "server.js"] + +Now when you edit server.js and rebuild, Docker reuses the cached node_modules layer and only re-copies your source. Build time drops from 60+ seconds to under 2 seconds. + +Cache Invalidation Demonstration +# First build — all layers built from scratch +docker build -t cache-demo . + +# Edit any source file... +echo 'console.log("v2")' >> server.js + +# Rebuild — watch which layers say 'CACHED' +docker build -t cache-demo . +# You will see: +# => CACHED [2/4] WORKDIR /app +# => CACHED [3/4] COPY package*.json ./ +# => CACHED [4/4] RUN npm install <-- this is the win! +# => [5/4] COPY . . <-- only this re-runs + +Layer Optimization Rules +Rule Why It Matters +Put rarely-changing instructions first Maximize cache hits. Base image, system packages, and dependencies change infrequently. +COPY package.json before COPY . . npm install/pip install are slow. Cache them separately from your changing source code. +Combine RUN commands with && Each RUN is a layer. Chaining commands reduces layer count and final image size. +Clean up in the same RUN apt-get cache must be removed in the same layer it was created, or it stays in the image. +Use .dockerignore Reduces build context size → faster COPY . . → less invalidation noise. +Prefer alpine base images Smaller base = fewer layers to pull, push, and cache. + +Combining RUN Commands +# BAD: 3 separate layers +RUN apt-get update +RUN apt-get install -y curl +RUN rm -rf /var/lib/apt/lists/* + +# GOOD: 1 layer — smaller image, cleaner cache +RUN apt-get update \ + && apt-get install -y curl \ + && rm -rf /var/lib/apt/lists/* + +Dockerfile Instruction Quick Reference + +Instruction Description +FROM Set the base image. Required as the first instruction. +WORKDIR Set (and create) the working directory for subsequent instructions. +COPY Copy files from build context into the image. +RUN Execute a command at build time. Creates a new layer. +EXPOSE Document the port the container listens on (informational only). +ENV KEY=value Set environment variables available at build and run time. +ARG NAME=default Define build-time variables passed with --build-arg. +CMD ["cmd","arg"] Default command when container starts. Overridable at docker run. +ENTRYPOINT ["cmd"] Fixed executable for the container. Args appended at docker run. +VOLUME ["path"] Create a mount point for persistent data. +USER name Set the user for subsequent RUN/CMD/ENTRYPOINT instructions. +LABEL key=value Add metadata to the image (author, version, description). + +Day 31 Complete +#90DaysOfDevOps | #DevOpsKaJosh | #TrainWithShubham +Happy Learning! — TrainWithShubham diff --git a/2026/day-32/day-32-volumes-networking.md b/2026/day-32/day-32-volumes-networking.md new file mode 100644 index 0000000000..640277b40d --- /dev/null +++ b/2026/day-32/day-32-volumes-networking.md @@ -0,0 +1,179 @@ +# Day 32 – Docker Volumes & Networking + +## Task 1: The Problem - Data Persistence Without Volumes + +**Experiment:** +- Ran a PostgreSQL container +- Created a database and inserted some test data +- Stopped and removed the container +- Ran a new container with the same image + +**Result:** Data was **NOT** persisted. + +**Why?** +Containers are ephemeral by design. When a container is removed, all its data (including databases, logs, files) is deleted. This is because container storage is tied to the container's writable layer, which only exists while the container runs. + +--- + +## Task 2: Named Volumes + +### Creating a Named Volume +```bash +docker volume create my-postgres-data +``` + +### Running PostgreSQL with the Volume +```bash +docker run -d \ + --name postgres-container \ + -e POSTGRES_PASSWORD=mysecretpassword \ + -v my-postgres-data:/var/lib/postgresql/data \ + postgres +``` + +### Verification Commands +```bash +docker volume ls +docker volume inspect my-postgres-data +``` + +### Testing Persistence +1. Connected to PostgreSQL and created a test database with data +2. Stopped and removed the container: `docker rm -f postgres-container` +3. Ran a new container with the same volume +4. **Data was still there!** + +**Why it works:** Named volumes persist independently of containers. The volume outlives any single container, so data persists across container lifecycles. + +--- + +## Task 3: Bind Mounts + +### Setup +1. Created a folder on host: `mkdir -p ~/nginx-html` +2. Created `index.html` inside with some content + +### Running Nginx with Bind Mount +```bash +docker run -d \ + --name nginx-bind \ + -p 8080:80 \ + -v ~/nginx-html:/usr/share/nginx/html \ + nginx +``` + +### Testing +- Accessed `http://localhost:8080` - page loaded +- Edited `index.html` on host, refreshed browser - **changes appeared immediately** + +### Named Volumes vs Bind Mounts + +| Aspect | Named Volumes | Bind Mounts | +|--------|---------------|-------------| +| Location | Docker-managed (`/var/lib/docker/volumes/`) | Host filesystem (any path) | +| Use Case | Database storage, app data | Development, config files | +| Host Access | Limited (Docker controls) | Full host access | +| Persistence | Survives container removal | Tied to host directory | +| Performance | Optimized for containers | Slightly slower (host I/O) | + +--- + +## Task 4: Docker Networking Basics + +### List All Networks +```bash +docker network ls +``` + +### Inspect Default Bridge +```bash +docker network inspect bridge +``` + +### Testing Communication on Default Bridge +```bash +# Run two containers on default bridge +docker run -d --name container1 nginx +docker run -d --name container2 alpine + +# Try pinging by name +docker exec container1 ping -c 3 container2 # FAILS - default bridge doesn't support DNS + +# Try pinging by IP +docker exec container1 ping -c 3 # WORKS - they're on same subnet +``` + +**Result:** +- By **name**: NO - containers cannot resolve each other's names on default bridge +- By **IP**: YES - containers can communicate by IP address + +--- + +## Task 5: Custom Networks + +### Create Custom Bridge Network +```bash +docker network create my-app-net +``` + +### Run Containers on Custom Network +```bash +docker run -d --name web --network my-app-net nginx +docker run -d --name app --network my-app-net alpine +``` + +### Test Communication +```bash +docker exec web ping -c 3 app # WORKS! +``` + +**Why does custom networking allow name-based communication?** +- Custom bridge networks have a built-in **embedded DNS server** +- Docker automatically assigns DNS entries for each container using its name +- Containers can resolve each other by service name (container name) +- This is essential for service discovery in multi-container applications + +--- + +## Task 6: Put It Together + +### Create the Setup +```bash +# Create custom network +docker network create fullstack-net + +# Run database with volume and network +docker run -d \ + --name mysql-db \ + -e MYSQL_ROOT_PASSWORD=password \ + -e MYSQL_DATABASE=testdb \ + -v mysql-data:/var/lib/mysql \ + --network fullstack-net \ + mysql:8 + +# Run app container on same network +docker run -d \ + --name my-app \ + --network fullstack-net \ + nginx +``` + +### Verify Communication +```bash +docker exec my-app ping -c 1 mysql-db # SUCCESS! +``` + +**Result:** The app container successfully reached the database using the container name (`mysql-db`). This demonstrates: +1. Custom networking provides DNS-based service discovery +2. Named volumes persist database data +3. Containers can communicate by name without knowing IP addresses + +--- + +## Summary + +- **Volumes** solve data persistence - named volumes survive container removal +- **Bind mounts** map host directories into containers - great for development +- **Default bridge** allows IP-based communication only +- **Custom networks** provide DNS-based service discovery - containers can reach each other by name +- Combining volumes + custom networks = production-ready multi-container setup \ No newline at end of file diff --git a/2026/day-33/day-33-compose.md b/2026/day-33/day-33-compose.md new file mode 100644 index 0000000000..f63d0b4e7c --- /dev/null +++ b/2026/day-33/day-33-compose.md @@ -0,0 +1,210 @@ +# Day 33 – Docker Compose: Multi-Container Basics + +## Task 1: Install & Verify + +```bash +# Check if Docker Compose is available +docker compose version + +# Output: +Docker Compose version v2.x.x +``` + +--- + +## Task 2: Your First Compose File + +### Create directory and docker-compose.yml +```bash +mkdir -p compose-basics +cd compose-basics +``` + +### docker-compose.yml +```yaml +version: '3.8' + +services: + nginx: + image: nginx + ports: + - "8080:80" + container_name: my-nginx +``` + +### Commands +```bash +# Start the service +docker compose up -d + +# Verify it's running +docker compose ps + +# Access in browser: http://localhost:8080 + +# Stop and remove +docker compose down +``` + +--- + +## Task 3: Two-Container Setup (WordPress + MySQL) + +### docker-compose.yml +```yaml +version: '3.8' + +services: + db: + image: mysql:8 + container_name: wordpress-db + environment: + MYSQL_ROOT_PASSWORD: mysecretpassword + MYSQL_DATABASE: wordpress + MYSQL_USER: wpuser + MYSQL_PASSWORD: wppassword + volumes: + - mysql-data:/var/lib/mysql + healthcheck: + test: ["CMD", "mysqladmin", "ping", "-h", "localhost"] + interval: 10s + timeout: 5s + retries: 5 + + wordpress: + image: wordpress:latest + container_name: wordpress-app + depends_on: + db: + condition: service_healthy + ports: + - "8080:80" + environment: + WORDPRESS_DB_HOST: db + WORDPRESS_DB_USER: wpuser + WORDPRESS_DB_PASSWORD: wppassword + WORDPRESS_DB_NAME: wordpress + volumes: + - ./wordpress-data:/var/www/html + +volumes: + mysql-data: +``` + +### Commands +```bash +# Start both services +docker compose up -d + +# View services +docker compose ps + +# Access WordPress at http://localhost:8080 +# Complete WordPress setup wizard +``` + +### Verify Data Persistence +```bash +# Stop services (but keep volumes) +docker compose down + +# Start again +docker compose up -d + +# WordPress data persists! +``` + +--- + +## Task 4: Compose Commands + +| Command | Description | +|---------|-------------| +| `docker compose up -d` | Start in detached mode | +| `docker compose ps` | View running services | +| `docker compose logs` | View all logs | +| `docker compose logs -f` | Follow logs in real-time | +| `docker compose logs nginx` | View specific service logs | +| `docker compose stop` | Stop without removing | +| `docker compose down` | Remove containers and networks | +| `docker compose down -v` | Remove everything including volumes | +| `docker compose build` | Rebuild images after changes | +| `docker compose build --no-cache` | Force rebuild without cache | +| `docker compose restart` | Restart all services | +| `docker compose restart nginx` | Restart specific service | + +--- + +## Task 5: Environment Variables + +### Method 1: Direct in docker-compose.yml +```yaml +services: + app: + image: myapp + environment: + - DB_HOST=localhost + - DB_PORT=5432 +``` + +### Method 2: Using .env file + +#### Create .env file +```bash +# .env +DB_HOST=db +DB_PORT=3306 +DB_USER=myuser +DB_PASSWORD=mypassword +``` + +#### Reference in docker-compose.yml +```yaml +version: '3.8' + +services: + app: + image: mysql:8 + environment: + MYSQL_ROOT_PASSWORD: ${DB_PASSWORD} + MYSQL_DATABASE: myapp + env_file: + - .env +``` + +### Verify Variables +```bash +# Check environment variables in running container +docker compose exec app env + +# Or check specific variable +docker compose exec app printenv DB_HOST +``` + +--- + +## Summary + +- **Docker Compose** orchestrates multi-container applications with a single YAML file +- **Services** in compose are the DNS names containers use to communicate +- **Volumes** persist data across `compose down` and `compose up` +- **Networks** are automatically created for all services +- **Environment variables** can be set directly or via `.env` file +- **Key commands**: `up`, `down`, `logs`, `ps`, `stop`, `build` + +### Common Workflow +```bash +# First time +docker compose up -d + +# After edits +docker compose down +docker compose up -d + +# Or rebuild without down +docker compose build +docker compose up -d + +# View logs +docker compose logs -f +``` \ No newline at end of file diff --git a/2026/day-34/day-34-compose-advanced.md b/2026/day-34/day-34-compose-advanced.md new file mode 100644 index 0000000000..e2e58a2e03 --- /dev/null +++ b/2026/day-34/day-34-compose-advanced.md @@ -0,0 +1,349 @@ +# Day 34 – Docker Compose: Real-World Multi-Container Apps + +Aaj ke din hum advanced Docker Compose seekhenge. Ye real projects jaisa hai - app + database + cache ke saath, health checks, restart policies, aur dependencies handle karna. + +--- + +## Task 1: Build Your Own App Stack (Web + DB + Cache) + +Maine Python Flask app liya jisme Postgres database aur Redis cache hai. + +### Project Structure +``` +myapp/ +├── app.py +├── requirements.txt +├── Dockerfile +└── docker-compose.yml +``` + +### app.py (Simple Flask App) +```python +from flask import Flask, jsonify +import os +import psycopg2 +import redis + +app = Flask(__name__) + +# Database connection +def get_db_connection(): + conn = psycopg2.connect( + host=os.environ['DB_HOST'], + database=os.environ['DB_NAME'], + user=os.environ['DB_USER'], + password=os.environ['DB_PASSWORD'] + ) + return conn + +# Redis connection +def get_redis_client(): + r = redis.Redis( + host=os.environ['REDIS_HOST'], + port=6379, + decode_responses=True + ) + return r + +@app.route('/') +def home(): + return jsonify({"message": "Hello from Flask + Postgres + Redis!"}) + +@app.route('/status') +def status(): + # Check DB + try: + conn = get_db_connection() + conn.close() + db_status = "OK" + except: + db_status = "FAIL" + + # Check Redis + try: + r = get_redis_client() + r.ping() + redis_status = "OK" + except: + redis_status = "FAIL" + + return jsonify({"db": db_status, "redis": redis_status}) + +if __name__ == '__main__': + app.run(host='0.0.0.0', port=5000) +``` + +### requirements.txt +``` +flask +psycopg2-binary +redis +gunicorn +``` + +### Dockerfile +```dockerfile +FROM python:3.11-slim + +WORKDIR /app + +COPY requirements.txt . +RUN pip install --no-cache-dir -r requirements.txt + +COPY . . + +EXPOSE 5000 + +CMD ["gunicorn", "--bind", "0.0.0.0:5000", "app:app"] +``` + +### docker-compose.yml +```yaml +version: '3.8' + +services: + web: + build: . + container_name: my-flask-app + ports: + - "5000:5000" + environment: + - DB_HOST=db + - DB_NAME=myapp + - DB_USER=postgres + - DB_PASSWORD=postgres + - REDIS_HOST=redis + depends_on: + - db + - redis + + db: + image: postgres:15-alpine + container_name: my-postgres + environment: + - POSTGRES_USER=postgres + - POSTGRES_PASSWORD=postgres + - POSTGRES_DB=myapp + volumes: + - postgres-data:/var/lib/postgresql/data + + redis: + image: redis:7-alpine + container_name: my-redis + +volumes: + postgres-data: +``` + +--- + +## Task 2: depends_on & Health Checks + +Ab hum dependency proper handle karenge taaki app tabhi start ho jab database ready ho, sirf start ho gayi ho. + +### docker-compose.yml with Healthcheck +```yaml +version: '3.8' + +services: + web: + build: . + depends_on: + db: + condition: service_healthy + # ... rest same + + db: + image: postgres:15-alpine + environment: + - POSTGRES_USER=postgres + - POSTGRES_PASSWORD=postgres + - POSTGRES_DB=myapp + volumes: + - postgres-data:/var/lib/postgresql/data + healthcheck: + test: ["CMD-SHELL", "pg_isready -U postgres"] + interval: 5s + timeout: 5s + retries: 5 + + redis: + image: redis:7-alpine + +volumes: + postgres-data: +``` + +### Key Points: +- **condition: service_healthy** - app tabhi start hoga jab DB "healthy" ho +- **healthcheck** - Docker yeh command run karega. Agar return karega "healthy" tab DB ready maana jayega +- **pg_isready** - Postgres ka command hai jo check karta hai ki DB ready hai ya nahi + +--- + +## Task 3: Restart Policies + +Restart policies se hum define karte hain ki container kaise restart ho. + +### Different Restart Policies: + +| Policy | Kab Restart Hota Hai | +|--------|---------------------| +| `no` | Kabhi nahi (default) | +| `always` | Hamesha, chahe koi bhi reason ho | +| `on-failure` | Sirf tabhi jab container fail ho | +| `unless-stopped` | Always jaise, par manually stop nahi karega | + +### Example with Restart Policies: +```yaml +services: + web: + build: . + restart: always + depends_on: + db: + condition: service_healthy + + db: + image: postgres:15-alpine + restart: always + # ... rest +``` + +### Testing: +```bash +# Container ko manually kill karein +docker kill my-postgres + +# Docker automatically restart kar dega! +docker ps # Dekho container wapas chal gaya +``` + +### Kab Use Karna Kya Hai: +- **always** - Database, cache jaisi important services ke liye +- **on-failure** - Background jobs, workers ke liye jo kabhi fail ho sakte hain +- **no** - Development ke liye jab manually control chahiye + +--- + +## Task 4: Custom Dockerfiles in Compose + +Pichle example mein humne build: . use kiya hai. Ab code change karke rebuild karte hain. + +### Steps: +```bash +# 1. Code change karein app.py mein +# 2. Rebuild karo +docker compose up --build + +# 3. Restart karo (agar already running hai) +docker compose restart web +``` + +### build options in compose: +```yaml +services: + web: + build: + context: ./app + dockerfile: Dockerfile.prod + # Or simple: build: ./app +``` + +--- + +## Task 5: Named Networks & Volumes + +Explicit networks aur volumes define karna zyada clear hota hai. + +### docker-compose.yml with explicit networks/volumes: +```yaml +version: '3.8' + +services: + web: + build: . + networks: + - frontend + - backend + labels: + - "app=myflask" + + db: + image: postgres:15-alpine + networks: + - backend + volumes: + - postgres-data:/var/lib/postgresql/data + + redis: + image: redis:7-alpine + networks: + - backend + +networks: + frontend: + driver: bridge + backend: + driver: bridge + +volumes: + postgres-data: +``` + +### Benefits: +- **Explicit networks** - Security ke liye zyada accha, alag-alag services alag networks mein +- **Labels** - Organization ke liye helpful, monitoring tools mein识别 ke liye +- **Named volumes** - Clear hai ki kaunsa volume kaunse service ke liye hai + +--- + +## Task 6: Scaling (Bonus) + +Docker compose se app ko scale kar sakte hain - multiple instances! + +### Try it: +```bash +docker compose up --scale web=3 -d +``` + +### What Happens? +- 3 web containers chalenge +- Lekin problem hai - saare 5000 port use karenge +- Error milega: "port is already allocated" + +### Problem: +- Docker compose port mapping sirf ek container ke liye allow karta hai +- Load balancer chahiye multiple replicas ke liye +- Docker Swarm ya Kubernetes mein ye automatically hota hai + +### Solution: +```yaml +# ports ke bajaye expose use karo (internal only) +services: + web: + expose: + - "5000" + # Ab scale karo + # Par phir bhi external access ke liye proxy/lb chahiye +``` + +--- + +## Summary - Key Commands: + +| Command | Purpose | +|---------|---------| +| `docker compose up -d` | Background mein chalana | +| `docker compose up --build` | Code change ke baad rebuild | +| `docker compose up --scale web=3` | Scale karne ki koshish | +| `docker compose logs -f` | Logs dekhna | +| `docker compose restart` | Restart all | +| `docker compose down` | Sabhi hata dena | + +### Key Concepts: +1. **depends_on with healthcheck** - App wait karega DB ready hone ka +2. **Restart policies** - Auto-restart ke liye +3. **Custom Dockerfile** - build: use karke +4. **Explicit networks** - Better security +5. **Scaling** - Port conflict issue hai simple compose mein \ No newline at end of file diff --git a/2026/day-35/day-35-multistage-hub.md b/2026/day-35/day-35-multistage-hub.md new file mode 100644 index 0000000000..3b3ed4afdc --- /dev/null +++ b/2026/day-35/day-35-multistage-hub.md @@ -0,0 +1,326 @@ +# Day 35 – Multi-Stage Builds & Docker Hub + +Aaj ke din hum seekhenge ki production-ready Docker images kaise banate hain - chhote, secure, aur sharing ke liye. Multi-stage builds aur Docker Hub dono interview mein bahut puchhte hain. + +--- + +## Task 1: The Problem with Large Images + +Jab hum normally Dockerfile likhte hain, toh bahut saare unnecessary files image mein aa jate hain. Result - bada image, slow deployments, security risks. + +### Example - Simple Node.js App + +Mere paas ek simple Node.js app hai: +```javascript +// index.js +const express = require('express'); +const app = express(); + +app.get('/', (req, res) => { + res.send('Hello Docker!'); +}); + +app.listen(3000, () => { + console.log('Server chal raha hai!'); +}); +``` + +### package.json +```json +{ + "name": "myapp", + "version": "1.0.0", + "main": "index.js", + "dependencies": { + "express": "^4.18.2" + }, + "devDependencies": {} +} +``` + +### Single Stage Dockerfile (Problem Wala) +```dockerfile +FROM node:18 + +WORKDIR /app + +COPY package*.json ./ +RUN npm install + +COPY . . + +EXPOSE 3000 + +CMD ["node", "index.js"] +``` + +### Build and Check Size: +```bash +docker build -t myapp-single . +docker images myapp-single +``` + +**Result:** Image size approx **1GB+** (node:18 image bada hai!) + +### Problem: +- Poora Node.js runtime aata hai +- Dev dependencies bhi included +- Compilation tools jo production mein chahiye nahi +- Security vulnerabilities zyada + +--- + +## Task 2: Multi-Stage Build (Solution) + +Multi-stage build mein hum do alag stages use karte hain: + +### Stage 1: Build (Builder) +- Dependencies install karo +- App build karo +- Compilation karo + +### Stage 2: Production +- Sirf final output copy karo +- Chhota base image use karo (alpine ya slim) + +### Multi-Stage Dockerfile: +```dockerfile +# Stage 1: Build Stage +FROM node:18-alpine AS builder + +WORKDIR /app + +COPY package*.json ./ +RUN npm install + +COPY . . +RUN npm run build # Agar build step chahiye + +# Stage 2: Production Stage +FROM node:18-alpine + +WORKDIR /app + +# Sirf production dependencies +COPY package*.json ./ +RUN npm install --production + +# Builder se sirf files copy karo +COPY --from=builder /app . + +EXPOSE 3000 + +USER node + +CMD ["node", "index.js"] +``` + +### Build and Check: +```bash +docker build -t myapp-multistage . +docker images myapp-multistage +``` + +### Compare Results: + +| Image Type | Size | +|------------|------| +| Single Stage (node:18) | ~1GB | +| Multi-Stage (node:18-alpine) | ~170MB | +| Multi-Stage with alpine | ~150MB | + +### Why So Much Smaller? + +1. **Alpine base** - 5MB ka base vs 900MB+ +2. **Production only** - dev dependencies nahi +3. **Only artifact** - sirf compiled code, naki source + build tools +4. **Fewer layers** - optimized Dockerfile + +--- + +## Task 3: Push to Docker Hub + +Ab image ko publicly share karne ke liye Docker Hub par push karte hain. + +### Step 1: Docker Hub Account Banayein +1. [hub.docker.com](https://hub.docker.com) jayein +2. Free account create karo +3. Username note karo (e.g., `myusername`) + +### Step 2: Terminal se Login +```bash +docker login + +# Output: +# Username: myusername +# Password: ******** +# Login Succeeded +``` + +### Step 3: Image Tag Karein +```bash +# Format: username/repository:tag +docker tag myapp-multistage myusername/myapp:latest +``` + +### Step 4: Push Karein +```bash +docker push myusername/myapp:latest +``` + +### Step 5: Verify - Pull from Anywhere +```bash +# Local se hata kar do +docker rmi myusername/myapp:latest + +# Hub se pull karo +docker pull myusername/myapp:latest + +# Run karo +docker run -p 3000:3000 myusername/myapp:latest +``` + +--- + +## Task 4: Docker Hub Repository Explore Karein + +Docker Hub website par jakar: + +1. **Repository dekho** - Tera image dikhega +2. **Description add karo** - "My Node.js app" +3. **Tags tab** dekho: + - `latest` - sabse latest version + - `v1.0`, `v1.1` - version numbers + - `latest` pull karne se latest milta hai + - Specific tag like `v1.0` se exact version milta hai + +### Tags ka Fayda: +```bash +# Latest +docker pull myusername/myapp:latest + +# Specific version +docker pull myusername/myapp:v1.0 +``` + +--- + +## Task 5: Image Best Practices + +Ab apne image ko aur behtar banayenge: + +### 1. Minimal Base Image +```dockerfile +# Bad - bada image +FROM node:18 + +# Good - chhota image +FROM node:18-alpine +``` + +### 2. Don't Run as Root +```dockerfile +FROM node:18-alpine + +RUN addgroup -g 1001 appgroup && \ + adduser -u 1001 -G appgroup -s /bin/sh -D appuser + +USER appuser +``` + +### 3. Combine RUN Commands (Reduce Layers) +```dockerfile +# Bad - alag-alag layers +RUN apt-get update +RUN apt-get install -y git +RUN apt-get clean + +# Good - ek hi command +RUN apt-get update && \ + apt-get install -y git && \ + apt-get clean && \ + rm -rf /var/lib/apt/lists/* +``` + +### 4. Specific Tags (Not Latest) +```dockerfile +# Bad +FROM node:latest + +# Good +FROM node:18-alpine +``` + +### Complete Optimized Dockerfile: +```dockerfile +# Build Stage +FROM node:18-alpine AS builder + +WORKDIR /app +COPY package*.json ./ +RUN npm install + +COPY . . + +# Production Stage +FROM node:18-alpine + +WORKDIR /app + +COPY package*.json ./ +RUN npm install --production + +COPY --from=builder /app . + +USER node + +EXPOSE 3000 + +CMD ["node", "index.js"] +``` + +### Check Size Difference: +```bash +# Before: ~1GB +# After optimization: ~150MB +``` + +--- + +## Summary + +### Multi-Stage Build Key Points: +1. **FROM ... AS builder** - Build stage define karein +2. **COPY --from=builder** - Sirf compiled files copy karo +3. **Alpine base** - Use karo for small size + +### Docker Hub Key Points: +1. **docker login** - Terminal se login +2. **docker tag** - Proper format mein tag karo +3. **docker push** - Hub par bhejo +4. **docker pull** - Kahi se bhi download karo + +### Image Optimization: +- Alpine base use karo +- Root user se bachho +- Layers combine karo +- Specific tags use karo +- Multi-stage se image chhota karo + +### Key Commands: +```bash +# Build +docker build -t myapp . + +# Tag for Hub +docker tag myapp myusername/myapp:v1.0 + +# Push +docker push myusername/myapp:v1.0 + +# Pull +docker pull myusername/myapp:v1.0 + +# Check size +docker images +``` \ No newline at end of file diff --git a/2026/day-36/day-36-docker-project.md b/2026/day-36/day-36-docker-project.md new file mode 100644 index 0000000000..4ebb04d0be --- /dev/null +++ b/2026/day-36/day-36-docker-project.md @@ -0,0 +1,401 @@ +# Day 36 – Docker Project: Dockerize a Full Application + +Aaj ke din hum ek purana application lekar usse complete Dockerize karenge. Isme Dockerfile, docker-compose.yml, aur sab kuchh likhna hai. Yeh woh kaam hai jo job par karna padega! + +--- + +## Task 1: Choose Your Application + +Maine **Python Flask Todo App** choose kiya hai because: +- Simple hai samajhne ke liye +- Database chahiye (PostgreSQL) +- Real-world project jaisa feel deta hai + +### App Features: +- Tasks create karo +- Tasks delete karo +- Database mein save hote hain + +--- + +## Task 2: Write the Dockerfile + +Maine Flask app ke liye **multi-stage build** use kiya hai taaki image chhoti rahe. + +### Project Structure: +``` +flask-todo/ +├── app.py +├── requirements.txt +├── .dockerignore +├── Dockerfile +├── docker-compose.yml +├── .env +└── README.md +``` + +### app.py: +```python +from flask import Flask, render_template_string, request, redirect, url_for +import psycopg2 +import os +from datetime import datetime + +app = Flask(__name__) + +def get_db_connection(): + conn = psycopg2.connect( + host=os.environ['DB_HOST'], + database=os.environ['DB_NAME'], + user=os.environ['DB_USER'], + password=os.environ['DB_PASSWORD'] + ) + return conn + +def init_db(): + conn = get_db_connection() + cur = conn.cursor() + cur.execute(''' + CREATE TABLE IF NOT EXISTS todos ( + id SERIAL PRIMARY KEY, + task VARCHAR(255) NOT NULL, + created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP + ) + ''') + conn.commit() + cur.close() + conn.close() + +HTML_TEMPLATE = ''' + + + + Todo App + + + +

📝 My Todo List

+
+ + +
+
    + {% for todo in todos %} +
  • + {{ todo[1] }} + Delete +
    • + {% endfor %} +
+

{{ todos|length }} tasks

+ + +''' + +@app.route('/') +def index(): + conn = get_db_connection() + cur = conn.cursor() + cur.execute('SELECT * FROM todos ORDER BY created_at DESC') + todos = cur.fetchall() + cur.close() + conn.close() + return render_template_string(HTML_TEMPLATE, todos=todos) + +@app.route('/add', methods=['POST']) +def add(): + task = request.form['task'] + conn = get_db_connection() + cur = conn.cursor() + cur.execute('INSERT INTO todos (task) VALUES (%s)', (task,)) + conn.commit() + cur.close() + conn.close() + return redirect(url_for('index')) + +@app.route('/delete/') +def delete(todo_id): + conn = get_db_connection() + cur = conn.cursor() + cur.execute('DELETE FROM todos WHERE id = %s', (todo_id,)) + conn.commit() + cur.close() + conn.close() + return redirect(url_for('index')) + +if __name__ == '__main__': + init_db() + app.run(host='0.0.0.0', port=5000) +``` + +### requirements.txt: +``` +flask +psycopg2-binary +gunicorn +``` + +### .dockerignore: +``` +__pycache__ +*.pyc +.git +.env +venv/ +``` + +### Dockerfile (Multi-Stage Build): +```dockerfile +# Stage 1: Build Stage +FROM python:3.11-slim AS builder + +WORKDIR /app + +# Install dependencies +COPY requirements.txt . +RUN pip install --no-cache-dir -r requirements.txt + +# Stage 2: Production Stage +FROM python:3.11-slim + +WORKDIR /app + +# Copy only what's needed +COPY --from=builder /usr/local/lib/python3.11/site-packages /usr/local/lib/python3.11/site-packages +COPY --from=builder /usr/local/bin /usr/local/bin +COPY . . + +# Non-root user create karo (security ke liye) +RUN useradd -m appuser && chown -R appuser:appuser /app +USER appuser + +EXPOSE 5000 + +CMD ["gunicorn", "--bind", "0.0.0.0:5000", "--workers", "4", "app:app"] +``` + +### Build locally: +```bash +docker build -t my-flask-todo . +docker run -p 5000:5000 my-flask-todo +``` + +--- + +## Task 3: Add Docker Compose + +Ab database, network, volumes sab add karte hain. + +### .env file: +```env +POSTGRES_USER=postgres +POSTGRES_PASSWORD=secretpassword +POSTGRES_DB=tododb +DB_HOST=db +``` + +### docker-compose.yml: +```yaml +version: '3.8' + +services: + web: + build: . + container_name: flask-todo-app + ports: + - "5000:5000" + environment: + - DB_HOST=db + - DB_NAME=${POSTGRES_DB} + - DB_USER=${POSTGRES_USER} + - DB_PASSWORD=${POSTGRES_PASSWORD} + depends_on: + db: + condition: service_healthy + restart: always + + db: + image: postgres:15-alpine + container_name: todo-postgres + environment: + - POSTGRES_USER=${POSTGRES_USER} + - POSTGRES_PASSWORD=${POSTGRES_PASSWORD} + - POSTGRES_DB=${POSTGRES_DB} + volumes: + - postgres-data:/var/lib/postgresql/data + healthcheck: + test: ["CMD-SHELL", "pg_isready -U postgres"] + interval: 5s + timeout: 5s + retries: 5 + restart: always + +networks: + default: + name: todo-network + +volumes: + postgres-data: +``` + +### Test locally: +```bash +docker compose up -d +# Open http://localhost:5000 +# Add some todos +docker compose down +docker compose up -d +# Data still there! +``` + +--- + +## Task 4: Ship It (Push to Docker Hub) + +### Step 1: Tag the image: +```bash +docker build -t yourusername/flask-todo:latest . +``` + +### Step 2: Login to Docker Hub: +```bash +docker login +# Enter username/password +``` + +### Step 3: Push: +```bash +docker push yourusername/flask-todo:latest +``` + +### Step 4: Check on Docker Hub: +- Go to hub.docker.com +- Tera repository dikhega +- Description add karo + +--- + +## Task 5: Test the Whole Flow + +Sab kuchh local se hata kar fresh se pull aur run karte hain. + +### Step 1: Remove local: +```bash +docker compose down -v +docker rmi yourusername/flask-todo:latest +``` + +### Step 2: Pull from Hub: +```bash +docker pull yourusername/flask-todo:latest +``` + +### Step 3: Run with compose: +```yaml +# Change docker-compose.yml image to: +image: yourusername/flask-todo:latest +# (remove build: .) + +docker compose up -d +``` + +### Step 4: Verify: +- Browser mein http://localhost:5000 +- App chal raha hai! + +--- + +## Challenges Faced & Solutions: + +1. **Database connection timing**: App start ho jata tha DB ready hone se pehle. + - **Solution**: Healthcheck lagaya aur `depends_on` with `condition: service_healthy` use kiya. + +2. **Permission issues**: Non-root user ke karne ke baad file access nahi ho raha tha. + - **Solution**: COPY ke baad chown kiya aur useradd kiya. + +3. **Environment variables**: Compose mein `.env` file se values nahi mil rahi thi. + - **Solution**: `environment:` mein `${VARIABLE}` format use kiya. + +--- + +## Final Image Size: + +| Metric | Size | +|--------|------| +| Original Python image | ~1GB | +| After multi-stage | ~180MB | +| Final optimized | ~170MB | + +--- + +## Docker Hub Link: + +**Repository:** https://hub.docker.com/r/yourusername/flask-todo + +--- + +## README.md: + +```markdown +# Flask Todo App + +Ek simple Todo application jo Flask aur PostgreSQL use karta hai. + +## Features +- Naye tasks add karo +- Tasks delete karo +- Database mein save hote hain + +## Run Locally with Docker Compose + +```bash +# Clone ya download karo +cd flask-todo + +# Run karo +docker compose up -d +``` + +Browser mein http://localhost:5000 open karo. + +## Environment Variables + +`.env` file mein: +- POSTGRES_USER +- POSTGRES_PASSWORD +- POSTGRES_DB + +## Pull from Docker Hub + +```bash +docker pull yourusername/flask-todo:latest +``` + +## Tech Stack +- Python Flask +- PostgreSQL +- Gunicorn +- Docker & Docker Compose +``` + +--- + +## Summary: + +1. **Dockerfile** - Multi-stage build, non-root user, alpine base +2. **docker-compose.yml** - DB, network, volumes, healthcheck, restart policy +3. **.env** - Environment variables +4. **.dockerignore** - Unnecessary files exclude +5. **Push to Hub** - Public sharing +6. **Test** - Fresh pull and run + +Isse poora project production-ready hai! \ No newline at end of file