How about this question that I asked? > Do you have some storm configuration setting pointing at /tmp/storm?
Those files don't seem specific to storm-core -- seems this is some cruft from a topology. Searching google for "pipeout file" implies they might be coming from Hive: - https://www.google.com/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#safe=off&q=pipeout%20file So do you have topologies using Hive? - Erik On Thu, Mar 24, 2016 at 12:45 AM, Igor Kuzmenko <[email protected]> wrote: > I'm using storm 0.10.0 > I recived few files from our system administrator, that's not actualy .tmp > files. They are all zero sized and named like this: > > *000f9b90-1057-458a-a979-a52fe89042a44788427259950756302.pipeout* > > *00064dd7-d565-4211-99e8-c9dc78fac0ff7990926303561578787.pipeout* > *00085e62-7012-4835-b646-55407e3330c68985771934554548937.pipeout* > > On Wed, Mar 23, 2016 at 10:21 PM, Erik Weathers <[email protected]> > wrote: > >> hi Igor, >> >> What is an example such file? (Maybe they are ".so" files that the java >> libraries you are using are stuffing there? e.g., the >> org.xerial.snappy:snappy-java library spews .so files all over /tmp for me.) >> >> What is the version of storm you are using? >> >> Do you have some storm configuration setting pointing at /tmp/storm? >> >> - Erik >> >> On Wed, Mar 23, 2016 at 9:29 AM, Igor Kuzmenko <[email protected]> >> wrote: >> >>> Today I get "*java.io.IOException: No space left on device*" because >>> there was no more inodes left. The reason is that I've got a thousands of >>> .tmp files under /tmp/storm created by storm. Why theres so much and what >>> for? >>> >>> >> >
