[GitHub] incubator-tephra pull request #35: (TEPHRA-219) Execute cross region calls i...

[gokulavasan]

GitHub user gokulavasan opened a pull request:

https://github.com/apache/incubator-tephra/pull/35

(TEPHRA-219) Execute cross region calls in Coprocessor as the login user

i) Fixes a problem where the pruneThread would exit if the state of the 
service is not yet set to RUNNING state. This also fixes the flakiness in the 
PruneUpperBoundSupplierTest which was caused due to the above problem.

ii) Load the txMaxLifeTimeMillis and pruneEnable properties dynamically.

iii) Add a hook around cross region calls in the PruneUpperBoundWriter.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gokulavasan/incubator-tephra 
feature/dynamic-loading-props

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-tephra/pull/35.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #35


commit 5fd4c6f54f9c17500788f1ae7bea38be073729fc
Author: Gokul Gunasekaran 
Date:   2017-02-12T03:42:02Z

Check all valid states

commit 4b7a837ae8584c18437984bf13579d31628f9487
Author: Gokul Gunasekaran 
Date:   2017-02-12T07:13:53Z

Load properties dynamically

commit 2c8b8952025adaa7cef96c90a9d60ffcce233da4
Author: Gokul Gunasekaran 
Date:   2017-02-12T07:41:58Z

TEPHRA-219 execute cross region calls in coprocessor as the login user

commit 9a120fe2db1a6e99f2d81dda00f99346a9cc4457
Author: Gokul Gunasekaran 
Date:   2017-02-12T07:54:45Z

We can;t guarantee to reload pruneTable and pruneFlushInterval since we use 
single thread across all regions and thus the thread might be already running




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (TEPHRA-216) Invalid Transaction List Pruning will not proceed if there are empty transactional tables

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/TEPHRA-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15862344#comment-15862344
 ] 

ASF GitHub Bot commented on TEPHRA-216:
---

Github user poornachandra commented on the issue:

https://github.com/apache/incubator-tephra/pull/34
  
Thanks @anew. I will squash the commits and then port changes to other 
compat modules.


> Invalid Transaction List Pruning will not proceed if there are empty 
> transactional tables
> -
>
> Key: TEPHRA-216
> URL: https://issues.apache.org/jira/browse/TEPHRA-216
> Project: Tephra
>  Issue Type: Sub-task
>Affects Versions: 0.11.0-incubating
>Reporter: Gokul Gunasekaran
>Assignee: Poorna Chandra
>
> Since empty table/regions might not undergo major compaction, the prune upper 
> bound of these regions will never have a value and thus will limit the 
> progress of invalid list transaction pruning.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] incubator-tephra issue #34: TEPHRA-216 Handle empty transactional regions du...

[anew]

Github user anew commented on the issue:

https://github.com/apache/incubator-tephra/pull/34
  
LGTM


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-tephra issue #34: TEPHRA-216 Handle empty transactional regions du...

[poornachandra]

Github user poornachandra commented on the issue:

https://github.com/apache/incubator-tephra/pull/34
  
Thanks @anew. I will squash the commits and then port changes to other 
compat modules.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---