[
https://issues.apache.org/jira/browse/OMID-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16808624#comment-16808624
]
Yonatan Gottesman commented on OMID-140:
----------------------------------------
Hi [~lhofhansl] there is a limit on the packet size the TSO can accept:
TSOChannelHandler.java:279
we can Increase max size - but still there will be a limit on transaction size,
and i understand it will wast memory if we dont use the whole buffer size.
How common are these large transactions of yours?
(I agree we should remove the "tx" from the printed log...)
> 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)
