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

Lars Hofhansl commented on OMID-140:
------------------------------------

{code}
19/04/01 16:45:31 ERROR client.TSOClient: Error on channel [id: 0x1cb51e14, 
/127.0.0.1:40984 :> localhost/127.0.0.1:54758]
java.nio.channels.ClosedChannelException
 at 
org.apache.phoenix.shaded.org.jboss.netty.channel.socket.nio.NioWorker.cleanUpWriteBuffer(NioWorker.java:645)
 at 
org.apache.phoenix.shaded.org.jboss.netty.channel.socket.nio.NioWorker.writeFromUserCode(NioWorker.java:372)
 at 
org.apache.phoenix.shaded.org.jboss.netty.channel.socket.nio.NioClientSocketPipelineSink.eventSunk(NioClientSocketPipelineSink.java:117)
 at 
org.apache.phoenix.shaded.org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendDownstream(DefaultChannelPipeline.java:771)
 at 
org.apache.phoenix.shaded.org.jboss.netty.channel.Channels.write(Channels.java:632)
 at 
org.apache.phoenix.shaded.org.jboss.netty.handler.codec.oneone.OneToOneEncoder.handleDownstream(OneToOneEncoder.java:70)
 at 
org.apache.phoenix.shaded.org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:591)
 at 
org.apache.phoenix.shaded.org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendDownstream(DefaultChannelPipeline.java:776)
 at 
org.apache.phoenix.shaded.org.jboss.netty.channel.Channels.write(Channels.java:632)
 at 
org.apache.phoenix.shaded.org.jboss.netty.handler.codec.oneone.OneToOneEncoder.handleDownstream(OneToOneEncoder.java:70)
 at 
org.apache.phoenix.shaded.org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:591)
 at 
org.apache.phoenix.shaded.org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendDownstream(DefaultChannelPipeline.java:776)
 at 
org.apache.phoenix.shaded.org.jboss.netty.channel.SimpleChannelHandler.writeRequested(SimpleChannelHandler.java:304)
 at 
org.apache.phoenix.shaded.org.jboss.netty.channel.SimpleChannelHandler.handleDownstream(SimpleChannelHandler.java:266)
 at 
org.apache.phoenix.shaded.org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:591)
 at 
org.apache.phoenix.shaded.org.jboss.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:582)
 at 
org.apache.phoenix.shaded.org.jboss.netty.channel.Channels.write(Channels.java:611)
 at 
org.apache.phoenix.shaded.org.jboss.netty.channel.Channels.write(Channels.java:578)
 at 
org.apache.phoenix.shaded.org.jboss.netty.channel.AbstractChannel.write(AbstractChannel.java:251)
 at 
org.apache.omid.tso.client.TSOClient$ConnectedState.sendRequest(TSOClient.java:767)
 at 
org.apache.omid.tso.client.TSOClient$ConnectedState.handleEvent(TSOClient.java:865)
{code}


> ServiceUnavailableException when the write set if is too large.
> ---------------------------------------------------------------
>
>                 Key: OMID-140
>                 URL: https://issues.apache.org/jira/browse/OMID-140
>             Project: Apache Omid
>          Issue Type: Bug
>            Reporter: Lars Hofhansl
>            Priority: Major
>
> In the debugger I see this:
> {code:java}
> java.util.concurrent.ExecutionException: 
> org.apache.omid.tso.client.ServiceUnavailableException: Number of retries 
> exceeded. This API request failed permanently
> {code}
> {code:java}
> Thrown from here:
> HBaseTransactionManager(AbstractTransactionManager).commitRegularTransaction(AbstractTransaction<CellId>)
>  line: 417   
> HBaseTransactionManager(AbstractTransactionManager).commit(Transaction) line: 
> 252     
> OmidTransactionContext.commit() line: 124     
> MutationState.commit() line: 1226     
> PhoenixConnection$3.call() line: 673  
> PhoenixConnection$3.call() line: 669  
> CallRunner.run(T, CallWrapper...) line: 53    
> PhoenixConnection.commit() line: 669  
> {code}
> In my case I tried with a write set of 2^20 (a bit over 1m) rows (that came 
> to 4m cells.)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to