What I guess might be happening is that your data may contain some text
data that pig is not fully parsing because the data contains characters
that pig uses as delimiters (i.e commas and curly brackets). Thus, you can
probably take a look at the data and see if you can find any of the
characters used by pig to distinguish values, bags, tuples. You also might
want to move this topic to the pig forums to see if anyone else has faced a
On Tue, Oct 2, 2012 at 5:26 AM, Björn-Elmar Macek <[EMAIL PROTECTED]>wrote:
> Hi again,
> i executed a slightly different script again, that included some more
> operations. The logs look similar, but this time i have 2 attempt files for
> the same job-package:
> (1) _temporary/_attempt_**201210021204_0001_r_000001_0/**part-r-00001
> (2) _temporary/_attempt_**201210021204_0001_r_000001_1/**part-r-00001
> For me it looks like 2 results of the same jobpackage - this time both
> being not empty as before, but with about blocksize which is about 700 mb.
> I hoped, that both files contained the same content, but "diff" showed me
> that this was not the case. I merged both files with a combination of "cat"
> and "sort -u": the result is a file of about 1.2 gb, which indicates for
> me, that there were many different lines. I suppose, that the cluster didnt
> manage to compute this part-file, tho i have no idea what makes this file
> so special, that it is always this one which is corrupt(?).
> The worst solution would be for me to simply ignore this error and
> continue working with the merged file. Is there anybody who has experienced
> similar things?
> If there is a way to fix this, i would love to know, how? Possible reasons
> for the problems are also very appreciated! :)
> Am 01.10.2012 22:36, schrieb Björn-Elmar Macek:
>> The script i now want to executed looks like this:
>> x = load 'tag_count_ts_pro_userpair' as (group:tuple(),cnt:int,times:**
>> y = foreach x generate *, moins.daysFromStart('2011-06-**01 00:00:00',
>> store y into 'test_daysFromStart';
>> The problem is, that i do not have the logs anymore due to space
>> constraints within the cluster. But i think i can explain the important
>> The script that created this data was a GROUP statement followed by a
>> FOREACH calculating a COUNT on the bag mentioned above as "times" which is
>> represented in the 2nd column named "cnt". The results were stored via a
>> simple "store".
>> The resulting pig calculation started as expected, but stoppped showing
>> me progress at a certain percentage. A "tail -f" on the hadoop/logs dir
>> revealed that the hadoop calculation progressed nontheless - although some
>> of the tasktrackers permanently vanished during the shuffle phase with the
>> committed/eof/mortbay exception and stopped at least producing any more log
>> output. As i really continiously watched the log i could see, that those
>> work packages were handled by the remaining servers after some of them
>> already calculated packages of progress 1.0. Even the cleanup phase in the
>> end was done, ALTHOUGH(!) the pig log didn't reflect the calculations of
>> the cluster. And since i found the file as output in hdfs i supposed the
>> missing pig progress log entries were simply pig problems. Maybe im wrong
>> with that.
>> But i did the calculations several times and this happened during every
>> Is there something wrong with the data or the calculations?
>> On Mon, 1 Oct 2012 13:01:41 -0700, Robert Molina <[EMAIL PROTECTED]>
>>> It seems that maybe the previous pig script didn't generate the output
>>> data or write correctly on hdfs. Can you provide the pig script you
>>> are trying to run? Also, for the original script that ran and
>>> generated the file, can you verify if that job had any failed tasks?
>>> On Mon, Oct 1, 2012 at 10:31 AM, Björn-Elmar Macek wrote:
>>> Hi Robert,