[jira] [Commented] (TEPHRA-282) Travis builds fail due to timeout
[ https://issues.apache.org/jira/browse/TEPHRA-282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16327573#comment-16327573 ] ASF GitHub Bot commented on TEPHRA-282: --- GitHub user anew opened a pull request: https://github.com/apache/incubator-tephra/pull/70 [TEPHRA-282] Split Travis build per compat module You can merge this pull request into a Git repository by running: $ git pull https://github.com/anew/incubator-tephra tephra-282-travis-timeout Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-tephra/pull/70.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 #70 commit 047c18a81cb17cbf544b0cd45dc109780075e9d0 Author: anew Date: 2018-01-16T18:46:23Z [TEPHRA-282] Split Travis build per compat module > Travis builds fail due to timeout > - > > Key: TEPHRA-282 > URL: https://issues.apache.org/jira/browse/TEPHRA-282 > Project: Tephra > Issue Type: Bug >Reporter: Andreas Neumann >Assignee: Andreas Neumann >Priority: Major > Fix For: 0.14.0-incubating > > > Travis has a hard-coded time limit of 50 minutes for a single job. With the > addition of the hbase-compat-1.4 module, we now regularly exceed that limit. > We need to break the script into multiple jobs. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] incubator-tephra pull request #70: [TEPHRA-282] Split Travis build per compa...
GitHub user anew opened a pull request: https://github.com/apache/incubator-tephra/pull/70 [TEPHRA-282] Split Travis build per compat module You can merge this pull request into a Git repository by running: $ git pull https://github.com/anew/incubator-tephra tephra-282-travis-timeout Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-tephra/pull/70.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 #70 commit 047c18a81cb17cbf544b0cd45dc109780075e9d0 Author: anew Date: 2018-01-16T18:46:23Z [TEPHRA-282] Split Travis build per compat module ---
[jira] [Commented] (TEPHRA-278) Support HBase 1.4
[ https://issues.apache.org/jira/browse/TEPHRA-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16327481#comment-16327481 ] Andrew Purtell commented on TEPHRA-278: --- Thanks! > Support HBase 1.4 > - > > Key: TEPHRA-278 > URL: https://issues.apache.org/jira/browse/TEPHRA-278 > Project: Tephra > Issue Type: New Feature >Reporter: Andrew Purtell >Assignee: Andrew Purtell >Priority: Major > Fix For: 0.14.0-incubating > > > Some abstract interfaces have additional methods in HBase 1.4, requiring some > minor updates. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (TEPHRA-282) Travis builds fail due to timeout
Andreas Neumann created TEPHRA-282: -- Summary: Travis builds fail due to timeout Key: TEPHRA-282 URL: https://issues.apache.org/jira/browse/TEPHRA-282 Project: Tephra Issue Type: Bug Reporter: Andreas Neumann Assignee: Andreas Neumann Fix For: 0.14.0-incubating Travis has a hard-coded time limit of 50 minutes for a single job. With the addition of the hbase-compat-1.4 module, we now regularly exceed that limit. We need to break the script into multiple jobs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TEPHRA-278) Support HBase 1.4
[ https://issues.apache.org/jira/browse/TEPHRA-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Neumann updated TEPHRA-278: --- Fix Version/s: 0.14.0-incubating > Support HBase 1.4 > - > > Key: TEPHRA-278 > URL: https://issues.apache.org/jira/browse/TEPHRA-278 > Project: Tephra > Issue Type: New Feature >Reporter: Andrew Purtell >Assignee: Andrew Purtell >Priority: Major > Fix For: 0.14.0-incubating > > > Some abstract interfaces have additional methods in HBase 1.4, requiring some > minor updates. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (TEPHRA-278) Support HBase 1.4
[ https://issues.apache.org/jira/browse/TEPHRA-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Neumann resolved TEPHRA-278. Resolution: Fixed > Support HBase 1.4 > - > > Key: TEPHRA-278 > URL: https://issues.apache.org/jira/browse/TEPHRA-278 > Project: Tephra > Issue Type: New Feature >Reporter: Andrew Purtell >Assignee: Andrew Purtell >Priority: Major > > Some abstract interfaces have additional methods in HBase 1.4, requiring some > minor updates. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TEPHRA-278) Support HBase 1.4
[ https://issues.apache.org/jira/browse/TEPHRA-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16327471#comment-16327471 ] ASF GitHub Bot commented on TEPHRA-278: --- Github user asfgit closed the pull request at: https://github.com/apache/incubator-tephra/pull/68 > Support HBase 1.4 > - > > Key: TEPHRA-278 > URL: https://issues.apache.org/jira/browse/TEPHRA-278 > Project: Tephra > Issue Type: New Feature >Reporter: Andrew Purtell >Assignee: Andrew Purtell >Priority: Major > > Some abstract interfaces have additional methods in HBase 1.4, requiring some > minor updates. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] incubator-tephra pull request #68: TEPHRA-278 Support HBase 1.4
Github user asfgit closed the pull request at: https://github.com/apache/incubator-tephra/pull/68 ---
[jira] [Commented] (TEPHRA-278) Support HBase 1.4
[ https://issues.apache.org/jira/browse/TEPHRA-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16327459#comment-16327459 ] Andreas Neumann commented on TEPHRA-278: OK, I will create a Jira for the build timeout. In the mean time I have built your branch locally and it passes for me, too. I will merge this and then fix the CI. > Support HBase 1.4 > - > > Key: TEPHRA-278 > URL: https://issues.apache.org/jira/browse/TEPHRA-278 > Project: Tephra > Issue Type: New Feature >Reporter: Andrew Purtell >Assignee: Andrew Purtell >Priority: Major > > Some abstract interfaces have additional methods in HBase 1.4, requiring some > minor updates. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TEPHRA-247) Avoid encoding the transaction multiple times
[ https://issues.apache.org/jira/browse/TEPHRA-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16327452#comment-16327452 ] Andreas Neumann commented on TEPHRA-247: Yes, the in-progress list can grow large. A would think it will rarely grow larger than a few thousand, and it will always reflect the load on the system. The invalid list, however, grows persistently and will not shrink when the load goes down. We have seen some instances where an ill-behaved client could create 10s of 1000s of invalids per day, and soon you have hundreds of thousands. These then impact the performance of the system even when the load is low. That is why we are focussing more on the invalid list. Do you have ideas on how to reduce the in-progress list overhead? > Avoid encoding the transaction multiple times > - > > Key: TEPHRA-247 > URL: https://issues.apache.org/jira/browse/TEPHRA-247 > Project: Tephra > Issue Type: Improvement > Components: core, manager >Affects Versions: 0.12.0-incubating >Reporter: Andreas Neumann >Assignee: Andreas Neumann >Priority: Major > Attachments: design.jpg > > > Currently, the same transaction object is encoded again and again for every > Get performed in HBase. It would be better to cache the encoded transaction > for the duration of the transaction and reuse it, -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TEPHRA-247) Avoid encoding the transaction multiple times
[ https://issues.apache.org/jira/browse/TEPHRA-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16326874#comment-16326874 ] Patrick Xiaoman Huang commented on TEPHRA-247: -- Hi Andreas, Agree as you described the scenario, my proposal seems little too complex and not that convincing. and agree that if we can avoid invalid list transfering that will be much less bytes to transfer. Another question, if there are many clients, will inProgress in tx be large? Thanks Patrick > Avoid encoding the transaction multiple times > - > > Key: TEPHRA-247 > URL: https://issues.apache.org/jira/browse/TEPHRA-247 > Project: Tephra > Issue Type: Improvement > Components: core, manager >Affects Versions: 0.12.0-incubating >Reporter: Andreas Neumann >Assignee: Andreas Neumann >Priority: Major > Attachments: design.jpg > > > Currently, the same transaction object is encoded again and again for every > Get performed in HBase. It would be better to cache the encoded transaction > for the duration of the transaction and reuse it, -- This message was sent by Atlassian JIRA (v7.6.3#76005)
