[
https://issues.apache.org/jira/browse/OMID-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16807276#comment-16807276
]
Lars Hofhansl commented on OMID-140:
------------------------------------
Also note that by default it would log the *entire* write and conflictfree
sets. I removed the logging. And I think we should generally do that only at
debug or even trace logging. Definitely not at the WARN level :)
> 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.util.concurrent.ExecutionException:
> org.apache.omid.tso.client.ServiceUnavailableException: Number of retries
> exceeded. This API request failed permanently
> {code}
> {code}
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
