Menü
Emergency rollback procedures when changes break the ISUPIPE application or benchmark fails
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
MCP tool reference — exec, benchmark_start, benchmark_status, note_write, etc. Use when: executing commands on VMs, running benchmarks, or recording findings
ISUCON13 contest manual — server topology, service management, benchmark execution, and rules. Use when: checking environment setup, running benchmarks, or understanding contest constraints
ISUPipe application manual — features, terms, constraints, and API specs. Use when: understanding the app domain, checking API behavior or MUST/MAY requirements
General strategy for identifying and adding missing database indexes in ISUCON web applications
General techniques for optimizing user icon/avatar image serving in ISUCON web applications
General techniques for identifying and fixing N+1 query problems in ISUCON web applications
| name | emergency-rollback |
| description | Emergency rollback procedures when changes break the ISUPIPE application or benchmark fails |
When a change breaks the application and the benchmark fails or score drops significantly.
# Check if the app is running
exec host="vm1" command="systemctl status isupipe-go --no-pager"
# Check app logs for errors
exec host="vm1" command="journalctl -u isupipe-go --no-pager -n 30 --since '5 minutes ago'"
# Check if nginx is running
exec host="vm1" command="sudo nginx -t && systemctl status nginx --no-pager"
# Check MySQL
exec host="vm1" command="systemctl status mysql --no-pager"
exec host="vm1" command="mysql -u isucon -pisucon -e 'SELECT 1'"
If Go code changes broke the build or runtime:
# Revert Go source to original
exec host="vm1" command="cd /home/isucon/isucon13/webapp/go && git checkout -- ."
# Rebuild
exec host="vm1" command="cd /home/isucon/isucon13/webapp/go && go build -o isupipe ."
# Restart
exec host="vm1" command="sudo systemctl restart isupipe-go"
If schema changes or data corruption occurred:
# Re-initialize the database (drops and recreates all tables)
exec host="vm1" command="cd /home/isucon/isucon13/webapp/sql && sudo -u isucon bash init.sh"
Warning: This resets all data AND removes any added indexes. Re-apply indexes after init.
# Check for syntax errors
exec host="vm1" command="sudo nginx -t"
# If broken, restore default config
exec host="vm1" command="cd /home/isucon/isucon13 && git checkout -- ../env/*/etc/nginx/"
exec host="vm1" command="sudo systemctl reload nginx"
# Remove custom config
exec host="vm1" command="sudo rm -f /etc/mysql/mysql.conf.d/isucon.cnf"
exec host="vm1" command="sudo systemctl restart mysql"
If multi-server setup is broken, return to single-server:
# Restore MySQL to vm1 only
exec host="vm2" command="sudo systemctl start mysql"
exec host="vm3" command="sudo systemctl start mysql"
# Point apps back to localhost
exec host="vm2" command="sudo sed -i 's|ISUCON13_MYSQL_DIALCONFIG_ADDRESS=.*|ISUCON13_MYSQL_DIALCONFIG_ADDRESS=127.0.0.1|' /home/isucon/env.sh && sudo systemctl restart isupipe-go"
exec host="vm3" command="sudo sed -i 's|ISUCON13_MYSQL_DIALCONFIG_ADDRESS=.*|ISUCON13_MYSQL_DIALCONFIG_ADDRESS=127.0.0.1|' /home/isucon/env.sh && sudo systemctl restart isupipe-go"
# Restart app on vm1
exec host="vm1" command="sudo systemctl start isupipe-go"
Re-initialize everything on all VMs:
for vm in vm1 vm2 vm3; do
exec host="$vm" command="cd /home/isucon/isucon13/webapp/go && git checkout -- . && go build -o isupipe . && sudo systemctl restart isupipe-go"
exec host="$vm" command="cd /home/isucon/isucon13/webapp/sql && sudo -u isucon bash init.sh"
exec host="$vm" command="sudo systemctl restart nginx mysql pdns"
done
# Pretest to verify everything works
benchmark_start options="--pretest-only"
benchmark_status
If pretest passes, run a full benchmark to confirm score is back to expected level.