Essay
A Release During the Monsoon
季风中的发布

Since dawn, the weather over Mumbai had been stubbornly still. By ten, India's southwest monsoon was tapping the office windows in Nariman Point, loud enough to break the silence between my keyboard and the monitor. At twenty-six, I was a software engineer three months into a backend team, responsible for a release everyone called small. The service sent appointment reminders, which sounded harmle
Rain on the twelfth floor
My first warning was not a crash. The graph showed request volume flattening while the delay histogram kept widening. I opened the queue dashboard and watched jobs marked delivered, then waiting, then delivered again. Each retry was polite, quick, and exactly wrong. The tea beside my mouse had cooled to a brown skin, so I made another cup of masala chai before touching the configuration.
A quiet graph can still hide a crowded queue.
The bottleneck was a database connection held open while each reminder checked for a duplicate record. Outside, traffic had thickened and people under umbrellas hurried toward the station. Inside, I rewrote the query, added an index, and sent the patch through staging. Then the metrics split in a way I did not trust: the success rate dipped, latency rose, and one worker still refused to finish.
The part after deploy
At 6:40, the rain softened to a fine gray veil. I ran the load test again, this time with a deliberately uneven arrival pattern, because real reminders did not arrive like a metronome. The whiteboard behind me filled with arrows I erased and drew again. My white shirt felt damp at the cuffs, and the room smelled faintly of wet concrete and chai.
The release went out before seven. For twelve minutes, nothing appeared in the incident channel. Then a slow job began to drain the queue without another retry. I watched it until the last row turned green, closed my laptop, and left the office while the local train was still running at its usual unreliable speed.
Tonight, the incident channel was empty, and that was enough.
By Saturday, the rain had thinned to a gray haze over Mumbai. I reached Bharatanatyam rehearsal with wet hair and sore calves, counted the beats under my breath, and stopped trying to make the rhythm repair the week. At home, I reheated yesterday's dal and rice, opened one small ticket while the masala chai was still hot, and closed the laptop before the work could become a second shift.
中文译文
从清晨起,孟买上空的天气一直闷得没有动静。到了十点,来自印度西南部的季风正敲打纳里曼波因特的办公室窗户,声音大得足以打断键盘和显示器之间的安静。二十六岁的我是一名软件工程师,加入后端团队三个月,负责一次大家口中很小的发布。这个服务负责发送预约提醒;原本听上去无害,直到同一分钟里涌进数千条请求。
十二楼的雨
最初的警告并不是宕机。图表上的请求量已经走平,延迟直方图却仍在扩张。我打开队列面板,看着任务先被标记为已送达,继而变成等待,随后再次送达。每一次重试都礼貌、迅速,而且错得离谱。鼠标旁的茶已经结出一层棕色薄皮,我重新泡了一杯玛莎拉茶,才去改配置。
安静的图表下,也可能挤满等待中的任务。
瓶颈出在数据库连接上:每条提醒检查重复记录时,连接都被占着。窗外,街上的人撑伞赶向车站;屏幕里,我重写查询、加了索引,再把补丁送进预发布环境。然后各项指标以我不信任的方式分开了:成功率下滑,延迟上升,仍有一个任务执意没有结束。
发布之后
六点四十分,雨变成一层灰色细雾。我重新跑压测,这次特意让请求不均匀地到达,因为现实里的提醒不会像节拍器那样抵达。我身后的白板写满箭头,我擦掉,又重新画过。白衬衫的袖口有些潮,房间里隐约是湿混凝土和茶的味道。
七点前发布完成。十二分钟里,事故频道没有任何动静。随后,一项缓慢的任务开始把队列排空,没有再触发一次重试。我看着最后一行变绿,合上电脑,在当地列车仍以一贯不可靠的速度运行时离开办公室。
今晚,事故频道一直空着,而这已经足够。
到了星期六,雨在孟买上方散成灰雾。我顶着一头湿发、带着酸痛的小腿去排练婆罗多舞,嘴上默数节拍,不再试图让节奏替我修补这一周。回到家,我重新热了昨天的豆咖喱和米饭,在玛莎拉茶还烫着的时候开了一张小工单,随后合上电脑,没让工作拖成第二班。






