I/O With Files That Aren't Files
I/O With Files That Aren't Files
Join the DZone community and get the full member experience.Join For Free
Sensu is an open source monitoring event pipeline. Try it today.
Recently at work I needed to search through our archived files and provide the results by the end of the day. Here’s the parameters of the request:
- The archive files are encrypted and stored in HDFS (Don’t ask why we store them in HDFS).
- The files vary in size form 3-9 GB.
- The total number of files to search was 300+
- It takes between 1 – 2 minutes to decrypt each file.
In the past there have been requests to search one archived file. In those cases we would copy the file out of HDFS to a server. Then run a shell script to decrypt the file and perform the search. The decrypting program requires 2 arguments: an encrypted file and a file to write the decrypted data to. This means the decrypted and encrypted file are on disk at the same time.
At an average rate of of 1.5 minutes to decrypt a single file, it was going to take 450 minutes (7.5 hours) for 300 files. To add to my dilema, there wasn’t enough time to write custom RecordReader. The only solution would be to stream the files in parallel. But there 2 problems with that approach:
- The server does not have enough space for 20 (10 encrypted and 10 decrypted) files at a time.
- The decrypting code does read from stdin or write to stdout.
What to do? Use named pipes of course!
A Crash Course in Named Pipes
Pipes are used to compose narrowly focused programs together to solve broader problems. For example :
In this example we are using annonymous pipes (desigated by the ‘|’ character). Pipes used on the command line or in scripts only live for the life of the current process. Named pipes are similar with these exceptions:
- You create named pipes with the command
- Can be re-used by mulitple processes.
- Namped pipes persist until deleted with the command
- Exist on the filesystem and appear as files to other processes.
- Allow for inter-process communication.
Here’s an example of creating a named pipe and how it looks on the filesystem:
Notice here the named pipe shows in the
ls results and the first column on the left is a
p . Once you don’t need a named pipe any more you simply delete it like you would a file with the command
My Solution with Named Pipes
First I created a file comprised of the paths to the archives. Then a script iterated over the file and ran 10 decryption/search processes in parallel. Once 10 processes were started, the script would wait until all 10 were done before starting another batch.
Here’s the code for the
processFile function is straight forward, there are several steps we should explain:
- Line 2: Create a variable with the basename of the encrypted file from the full path.
- Line 3: Create a variable of the name of the encrypted file less the
- Lines 5,6: Create named pipes for the encrypted and decrypted file.
- Line 8: Stream the encrypted file from HDFS and redirect to the encrypted named pipe and background the process.
- Line 9: Run the
catcommand on the decrypted file. Then pipe the results to
awkand search for the information in question. This is also backgrounded.
- Line 11: Invoke the decryption script with the required file parameters.
- Line 12: After decrypting and searching the file, delete the named pipes.
Using named pipes enabled me to decrypt and search of 300+ files in roughly 1.5 hours. I also avoided the space issue by never having to land a file on disk. While named pipes aren’t needed every day, they are a useful tool to have in your arsenal.
Published at DZone with permission of Bill Bejeck , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.