Mailing-List: contact dev-help@pig.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@pig.apache.org
Date: Wed, 24 Oct 2012 16:54:14 +0000 (UTC)
From: "Cheolsoo Park (JIRA)" <jira@apache.org>
To: pig-dev@hadoop.apache.org
Message-ID: <480929300.22606.1351097654470.JavaMail.jiratomcat@arcas>
In-Reply-To: <561992199.14417.1350962112169.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (PIG-2999) Regression after PIG-2975:
 BinInterSedesTupleRawComparator secondary sort failing
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/PIG-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13483387#comment-13483387 ] 

Cheolsoo Park commented on PIG-2999:
------------------------------------

On my other jenkins jobs, I actually see TestJobSubmission.testReducerNumEstimation failed once.
{code}
12/10/24 02:30:56 FATAL master.HMaster: Unhandled exception. Starting shutdown.
java.net.BindException: Address already in use
	at sun.nio.ch.Net.bind(Native Method)
	at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:126)
	at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59)
	at org.mortbay.jetty.nio.SelectChannelConnector.open(SelectChannelConnector.java:216)
	at org.apache.hadoop.http.HttpServer.start(HttpServer.java:564)
	at org.apache.hadoop.hbase.master.HMaster.startServiceThreads(HMaster.java:767)
	at org.apache.hadoop.hbase.master.HMaster.finishInitialization(HMaster.java:488)
	at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:338)
	at java.lang.Thread.run(Thread.java:662)
{code}
In my case, it was due to a port number conflict. HBase master couldn't get started.
                
> Regression after PIG-2975: BinInterSedesTupleRawComparator secondary sort failing
> ---------------------------------------------------------------------------------
>
>                 Key: PIG-2999
>                 URL: https://issues.apache.org/jira/browse/PIG-2999
>             Project: Pig
>          Issue Type: Bug
>    Affects Versions: 0.11, 0.12
>            Reporter: Koji Noguchi
>            Assignee: Jonathan Coveney
>         Attachments: pig-2999-v1.txt, pig-2999-v2.txt
>
>
> I think I broke the build from PIG-2975.  I see couple of tests failing at BinInterSedesTupleRawComparator. 
> {noformat}
> 12/10/22 22:26:15 WARN mapred.LocalJobRunner: job_local_0022
> java.nio.BufferUnderflowException
> 	at java.nio.Buffer.nextGetIndex(Buffer.java:478)
> 	at java.nio.HeapByteBuffer.getLong(HeapByteBuffer.java:387)
> 	at org.apache.pig.data.BinInterSedes$BinInterSedesTupleRawComparator.compareBinInterSedesDatum(BinInterSedes.java:829)
> 	at org.apache.pig.data.BinInterSedes$BinInterSedesTupleRawComparator.compareBinSedesTuple(BinInterSedes.java:732)
> 	at org.apache.pig.data.BinInterSedes$BinInterSedesTupleRawComparator.compare(BinInterSedes.java:695)
> 	at org.apache.pig.backend.hadoop.executionengine.mapReduceLayer.PigSecondaryKeyComparator.compare(PigSecondaryKeyComparator.java:78)
> 	at org.apache.hadoop.mapred.Merger$MergeQueue.lessThan(Merger.java:373)
> 	at org.apache.hadoop.util.PriorityQueue.downHeap(PriorityQueue.java:139)
> 	at org.apache.hadoop.util.PriorityQueue.adjustTop(PriorityQueue.java:103)
> 	at org.apache.hadoop.mapred.Merger$MergeQueue.adjustPriorityQueue(Merger.java:335)
> 	at org.apache.hadoop.mapred.Merger$MergeQueue.next(Merger.java:350)
> 	at org.apache.hadoop.mapred.ReduceTask$4.next(ReduceTask.java:625)
> 	at org.apache.hadoop.mapreduce.ReduceContext.nextKeyValue(ReduceContext.java:117)
> 	at org.apache.hadoop.mapreduce.ReduceContext.nextKey(ReduceContext.java:92)
> 	at org.apache.hadoop.mapreduce.Reducer.run(Reducer.java:175)
> 	at org.apache.hadoop.mapred.ReduceTask.runNewReducer(ReduceTask.java:649)
> 	at org.apache.hadoop.mapred.ReduceTask.run(ReduceTask.java:417)
> 	at org.apache.hadoop.mapred.LocalJobRunner$Job.run(LocalJobRunner.java:260)
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira