{"id":9564,"date":"2018-08-08T07:00:53","date_gmt":"2018-08-08T11:00:53","guid":{"rendered":"https:\/\/qxf2.com\/blog\/?p=9564"},"modified":"2018-08-13T06:43:02","modified_gmt":"2018-08-13T10:43:02","slug":"exploring-wallaroo-giles-sender","status":"publish","type":"post","link":"https:\/\/qxf2.com\/blog\/exploring-wallaroo-giles-sender\/","title":{"rendered":"Exploring Wallaroo – Giles Sender"},"content":{"rendered":"

We have been exploring Wallaroo<\/a>, a framework that makes it easy to handle streaming data and write event processing applications quickly. Wallaroo’s examples and documentation are excellent. They cover the core concepts well. But their documentation is sparse for certain tools that Wallaroo has developed to make it easy to independently test the developed application. One such example is the Giles Sender that is used in all the examples. This post is for folks who want to know Giles Sender better.<\/p>\n

\n

Overview<\/h3>\n

1. Setup
\n2. Generate an input binary file
\n3. Run sender and check the output
\n4. Rerun the sender
\n5. Send an exact number of messages in our input binary file
\n6. Control the batch size and interval
\n7. Repeat your messages<\/p>\n

\n

1. Setup<\/strong><\/p>\n

We will rely on Wallaroo’s existing alphabet<\/a> application to help us understand the Giles Sender better. To follow along, make sure you are setup with Wallaroo + Python in Docker<\/a>. The setup instructions are clear and easy to follow. <\/p>\n

Note:<\/strong> In the steps below, we are making you open up multiple terminal prompts – one each for the sender, receiver and the application. We are doing this to make it extremely clear about what each component is doing.<\/p>\n

Once you are done with the Docker setup<\/p>\n

a. Start the Docker container by running the command:<\/p>\n

\r\ndocker run --rm -it --privileged -p 4000:4000 \\\r\n-v \/tmp\/wallaroo-docker\/wallaroo-src:\/src\/wallaroo \\\r\n-v \/tmp\/wallaroo-docker\/python-virtualenv:\/src\/python-virtualenv \\\r\n--name wally \\\r\nwallaroo-labs-docker-wallaroolabs.bintray.io\/release\/wallaroo:0.5.1\r\n<\/pre>\n
You should see an output similar to the image below:<\/p>\n
\"Wallaroo:<\/p>\n
b. Start the data receiver<\/p>\n
In a new terminal prompt, enter the container<\/p>\n
\r\ndocker exec -it wally env-setup\r\n<\/pre>\n
You should see the prompt within the container. In the prompt of the Docker container, start the receiver:<\/p>\n
\r\ndata_receiver --ponythreads=1 --ponynoblock \\\r\n  --listen 127.0.0.1:7002\r\n<\/pre>\n
Leave this terminal prompt open. Once we run our application and start our sender, you will see the result of sending messages to our alphabet application on this prompt.<\/p>\n
c. Start the alphabet application:<\/p>\n
In a new terminal prompt, as usual, enter the container<\/p>\n
\r\ndocker exec -it wally env-setup\r\n<\/pre>\n
Then, in the prompt of the Docker container, start the application:<\/p>\n
\r\nmachida --application-module alphabet --in 127.0.0.1:7010 \\\r\n  --out 127.0.0.1:7002 --metrics 127.0.0.1:5001 --control 127.0.0.1:6000 \\\r\n  --external 127.0.0.1:5050 --cluster-initializer --data 127.0.0.1:6001 \\\r\n  --name worker-name --ponythreads=1 --ponynoblock\r\n<\/pre>\n
You should see an output that looks something like the screenshot below:<\/p>\n
\"starting<\/p>\n
d. Prepare the sender:<\/p>\n
We will be using this terminal prompt through this blog post. In a new terminal prompt, as usual, enter the container<\/p>\n
\r\ndocker exec -it wally env-setup\r\n<\/pre>\n
Then, in the prompt of the Docker container, go to the alphabet application’s directory<\/p>\n
\r\ncd wallaroo\/examples\/python\/alphabet\/\r\n<\/pre>\n
This is the terminal prompt we will use in all subsequent steps.<\/p>\n
\n
2. Generate an input binary file<\/strong><\/p>\n
Wallaroo’s alphabet application uses a votes.msg<\/code> file as input. We will produce our own input binary file with limited data. This will make it easy for us to predict the output and thereby easily associate the output result with the changes we make when calling the sender.<\/p>\n
The alphabet application expects 9-byte messages:
\na) a 4-byte header that has just the length of the payload
\nb) a 1-byte alphabet
\nc) a 4-byte number that represents the number of votes for the alphabet<\/p>\n
To make things easy for us, we will design the file to have 52 messages. The first 26 messages will be an alphabet and the number 1. The second 26 messages will be an alphabet and the number 2.<\/p>\n
Save the following code as (say) generate_binary_votes.py<\/code> in your \/src\/wallaroo\/examples\/python\/alphabet directory.<\/p>\n
\r\n\"\"\"\r\nA scratch script to produce a file similar to votes.msg for Wallaroo's alphabet application\r\n\r\nDESIGN:\r\n1. Open a file fake_votes.msg in binary format\r\n2. Write 5 byte messages alphabet,vote \r\n3. Prepend a header with the number 5 (unsigned int) in it because all messages are 5 bytes\r\n4. Write this binary string to a file\r\n5. To make it easy to test for correctness, we will design the file to have only 52 messages \r\n6. The first 26 messages will be an alphabet and the number 1\r\n7. The second 26 messages will be an alphabet and the number 2\r\n\"\"\"\r\n\r\nimport string\r\nimport struct\r\n\r\ndef generate_alphabet_input(filename):\r\n    \"Generate a binary file with alphabets and votes\"\r\n    alphabets = list(string.ascii_lowercase)\r\n    with open(filename,'wb') as fp: \r\n        for i in range(1,3):\r\n            for alphabet in alphabets:\r\n                msg = struct.pack('>IsI',5,alphabet,i)\r\n                fp.write(msg)\r\n\r\n\r\n#----START OF SCRIPT\r\nif __name__=='__main__':\r\n    generate_alphabet_input('fake_votes.msg')\r\n<\/pre>\n
Now, run the python script to produce a new 468 byte (=52*9) binary input file called fake_votes.msg<\/code>.<\/p>\n
\r\npython generate_binary_votes.py\r\n<\/pre>\n
At the end of this step, you should have a fake_votes.msg<\/code> file in your current directory.<\/p>\n
3. Run sender and check the output<\/strong>
\nLet us run sender and make sure we have a useful input file. We will set the messages<\/code> argument to be 52 to send all messages in the file. This will make it clear that the messages in our file are being relayed and processed correctly. We expect every alphabet to have a vote count of 1 after the first 26 messages and a vote count of 3 (=1+2) once the second half of our input file has been processed. To do this, on your sender’s terminal prompt, run the following command:<\/p>\n
\r\nsender --host 127.0.0.1:7010 --file fake_votes.msg \\\r\n  --messages 52 --binary --msg-size 9 --ponythreads=1 \\\r\n  --ponynoblock --no-write\r\n<\/pre>\n
Observe the output in the receiver’s terminal prompt. You may need to scroll through. You will notice the first 26 lines of the output show each alphabet with a score of 1. The next 26 messages will show each alphabet listed with a score of 3.<\/p>\n
\"example<\/p>\n
4. Rerun the sender<\/strong>
\nWe are going to rerun the sender. Why?? To verify that the state is saved and that the votes get updated when new messages come along. <\/p>\n
\r\nsender --host 127.0.0.1:7010 --file fake_votes.msg \\\r\n  --messages 52 --binary --msg-size 9 --ponythreads=1 \\\r\n  --ponynoblock --no-write\r\n<\/pre>\n
Observe the output in the receiver’s terminal prompt. The final values of votes for each alphabet should be 6 (=3+3). The vote count before we reran the sender was 3 and by running the sender, we added 3 (=1+2) more votes to each alphabet.<\/p>\n
5. Send an exact number of messages in our input binary file<\/strong>
\nThe sender allows you to specify exactly how many messages should be sent to the application. In this step, we will send only 26 messages even though we have 52 messages in it.<\/p>\n
\r\nsender --host 127.0.0.1:7010 --file fake_votes.msg \\\r\n  --messages 26 --binary --msg-size 9 --ponythreads=1 \\\r\n  --ponynoblock --no-write\r\n<\/pre>\n
The first 26 messages in our file have an alphabet and the number 1. That means, we expect the vote count in our output to be 7 (=6+1) once we run the above command.<\/p>\n
6. Control the batch size and interval<\/strong>
\nSometimes, when testing our streaming application, we end up using really large files. It makes little sense to read or process the entire file all at once. So Giles Sender allows us to control the rate at which to send input messages by providing two arguments – batch-size<\/code> and interval<\/code>. The batch-size<\/code> argument is helpful when you are reading really large input files that cannot be processed all at once. Our example is laughably small and does not lend itself to illustrating this use case well. Instead, we will make our interval<\/code> really large (1-second) to illustrate that the output gets updated by a batch-size<\/code> number of messages per interval<\/code> nanoseconds. To do so, run the following command<\/p>\n
\r\nsender --host 127.0.0.1:7010 --file fake_votes.msg   \\\r\n--batch-size 1 --interval 1_000_000_000 --messages 52 \\\r\n--binary --msg-size 9 --ponythreads=1 --ponynoblock --no-write\r\n<\/pre>\n
If things are going well, you will observe that every one second (or 1_000_000_000 nano-seconds), you will see one updated message on your receiver screen. If you had set batch-size<\/code> to 2, you would have seen two updated messages every second. At the end of this step, the vote count for each alphabet should be 10 (=7+3).<\/p>\n
7. Repeat your messages<\/strong>
\nThere is another common use case when testing a streaming application. You need to use a small set of well-designed messages and repeat them many times. To do this, you can simply use the repeat<\/code> argument. In this example, we will send 520 messages by simply using the 52 messages we created. To do so, run<\/p>\n
\r\nsender --host 127.0.0.1:7010 --file fake_votes.msg \\\r\n  --messages 520 --binary --msg-size 9 --repeat \\\r\n  --ponythreads=1 --ponynoblock --no-write\r\n<\/pre>\n
At the end of this step, the final vote count for each alphabet should be 40 (=10 + 3*10)<\/p>\n
\n
By creating a simple input file and then playing around with the messages<\/code>, batch-size<\/code>, interval<\/code> and repeat<\/code> arguments, we managed to understand how to use the Giles Sender better to test streaming applications written with Wallaroo.<\/p>\n
\n
References<\/h3>\n
1. Giles Sender documentation<\/a><\/p>\n
\n","protected":false},"excerpt":{"rendered":"
We have been exploring Wallaroo, a framework that makes it easy to handle streaming data and write event processing applications quickly. Wallaroo’s examples and documentation are excellent. They cover the core concepts well. But their documentation is sparse for certain tools that Wallaroo has developed to make it easy to independently test the developed application. One such example is the […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[18,154],"tags":[],"class_list":["post-9564","post","type-post","status-publish","format-standard","hentry","category-python","category-wallaroo"],"_links":{"self":[{"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/posts\/9564","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/comments?post=9564"}],"version-history":[{"count":21,"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/posts\/9564\/revisions"}],"predecessor-version":[{"id":9629,"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/posts\/9564\/revisions\/9629"}],"wp:attachment":[{"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/media?parent=9564"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/categories?post=9564"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/tags?post=9564"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}