In order to get the log data to our logs processors, we’ll have two different components
operating on the data. The first is a script that will be taking the log files and
putting them in Redis under named keys, publishing the names of the keys to a chat
channel using our group chat method from section 6.5.2, and waiting for notification
when they’re complete (to not use more memory than our Redis machine has). It’ll
be waiting for a notification that a key with a name similar to the file stored in Redis
has a value equal to 10, which is our number of aggregation processes. The function
that copies logs and cleans up after itself is shown in the following listing.
Copying logs to Redis requires a lot of detailed steps, mostly involving being careful
to not put too much data into Redis at one time and properly cleaning up after ourselves
when a file has been read by all clients. The actual aspect of notifying logs processors
that there’s a new file ready is easy, but the setup, sending, and cleanup are
By continuing to use this site, you consent to our updated privacy agreement as described here. You can change your cookie settings at any time as described here but parts of our site will not function correctly without them.