You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tephra.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/02/01 00:23:51 UTC
[jira] [Commented] (TEPHRA-212) CompactionState
#savePruneUpperBoundForRegion put call might because problems if regions
are not available
[ https://issues.apache.org/jira/browse/TEPHRA-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15847770#comment-15847770 ]
ASF GitHub Bot commented on TEPHRA-212:
---------------------------------------
Github user poornachandra commented on a diff in the pull request:
https://github.com/apache/incubator-tephra/pull/29#discussion_r98804704
--- Diff: tephra-hbase-compat-1.1-base/src/main/java/org/apache/tephra/hbase/coprocessor/TransactionProcessor.java ---
@@ -324,9 +326,14 @@ public InternalScanner preCompactScannerOpen(ObserverContext<RegionCoprocessorEn
TxConstants.TransactionPruning.DEFAULT_PRUNE_ENABLE);
String pruneTable = conf.get(TxConstants.TransactionPruning.PRUNE_STATE_TABLE,
TxConstants.TransactionPruning.DEFAULT_PRUNE_STATE_TABLE);
- compactionState = new CompactionState(c.getEnvironment(), TableName.valueOf(pruneTable));
- LOG.debug("Automatic invalid list pruning is enabled. Compaction state will be recorded in table " +
- pruneTable);
+ long pruneFlushInterval = TimeUnit.SECONDS.toMillis(
--- End diff --
This line, and the line above getting `pruneTable` can also move into the if condition, right?
> CompactionState #savePruneUpperBoundForRegion put call might because problems if regions are not available
> ----------------------------------------------------------------------------------------------------------
>
> Key: TEPHRA-212
> URL: https://issues.apache.org/jira/browse/TEPHRA-212
> Project: Tephra
> Issue Type: Bug
> Affects Versions: 0.11.0-incubating
> Reporter: Gokul Gunasekaran
> Assignee: Gokul Gunasekaran
> Fix For: 0.11.0-incubating
>
>
> If the regions corresponding to prune state table are not available, trying to do a put to that table might cause multiple retries etc and might cause issues. Instead of doing this write in a synchronous fashion, this should be done asynchronously.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)