I’ve known about tmux for some time now, but I kept putting off working with it. Lately I’ve started looking at the Processor API available in Kafka. After opening up 4-5 terminal windows (Zookeeper, Kafka, sending messgaes, recieving messages) and toggling in between them, I quickly realized I needed a way to open up these terminal sessions at one time and have them centralized. I had the perfect use case to use tmux! This post is about scripting tmux to save time during devlopment, in this case working with kafka.
In this post we are going to assume the reader is alreay familiar with zookeeper and kafka.
Before we start it’s helpful to know how we can install tmux. Tmux can be downloaded from the main site. In my case I’m using a mac so I used homebrew –
brew install tmux.
I wanted a script to create the following workspace:
- Zookeeper running in it’s own pane.
- Kafka server running in it’s own pane.
- A separate pane to send messages.
- A separate pane to receive messages.
- Finally a pane to run my kafka-processor code or perform ad-hoc tasks.
I wanted to have zookeeper and kafka start automatically, the message producer and consumer I would be stopping and starting as needed. But I would like each respective pane to cd to the base kafka install directory. Once I found the relevant tmux commands it was simple to set up. Here’s the script:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34
While in depth coverage of tmux is beyond the scope of this post, it will be helpful to give a brief description of the tmux commands in the script.
There are serveral
split-window commands in the script and they do what you’d expect, split the window either horizontally or vertically. What’s not so obvious is that
split-window -v splits the window horizontally and
split-window -h splits vertically. Tmux sees the resulting panes differently than we humans. When the window is divided horizontally, two panes stacked on top of each other vertically and for vertical splits, panes are horizontally adjacent to each other. There is one final note about splitting a window into panes that needs mentioning. When the
split-window command is issued the cursor ends up in the most recently created pane. This is important to keep in mind if you are going to issue additional commands but don’t want them executed in the pane just created.
By default, tmux numbers the panes in a given window starting at 0. If the initial window is split in two panes horizontally, the top pane is still 0, and the bottom half is now number 1. While this seems very natural, when additional panes are split in different areas, the numbering may seem confusing. Just keep in mind panes are numbered in order of creation.
Sending Commands to Panes
Finally we have the
send-keys -t N <some command> commands in the script. This is so we can target a particular pane with the given command. In our case we want 4 of our panes to be in the base kakfa install directory so we issue the
tmux send-keys -t N "cd $KAFKA_DIR" C-m command. There are 4 such commands, each one with a specific target pane 1-4. We want to start zookeeper in pane 1 so the
tmux send-keys -t 1 "$START_ZK $ZK_PROPS" C-m command is used. To start the kafka server we issue a very similar command, except pane 2 is the target.
Final Tmux – Kafka Results
Here’s a screen shot of the final results of running the the kafka-tmux script. The numbers in the panes are for illustration purposes only.
This has been a quick tour of tmux. It is woefully incomplete and only scratches the surface on what we can do with tmux and how it can be configured. I just wanted to share my script in case someone might find it helpful. Thanks for your time.