[jira] [Updated] (ACCUMULO-3329) Consider consolidation of "timing" classes
[ https://issues.apache.org/jira/browse/ACCUMULO-3329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Owens updated ACCUMULO-3329: - Description: We have a number of "timing" classes in or used by the codebase * org.apache.accumulo.core.util.StopWatch * org.apache.accumulo.core.util.OpTimer * Traces * Guava's Stopwatch I'm assuming that consolidation of all of the timings into Traces would be the best (assuming that if we care about the timing of a given operation implies that twe would also care about the timing of the "bigger picture"). If we can remove some of our timer classes, that would be great. Not suggesting that we forcibly prevent the use of Stopwatches/TImers in the codebase entirely -- just where it makes sense. was: We have a number of "timing" classes in or used by the codebase * org.apache.accumulo.core.util.StopWatch * org.apache.accumulo.core.util.OpTimer * Traces * Guava's Stopwatch I'm assuming that consolidation of all of the timings into Traces would be the best (assuming that if we care about the timing of a given operation implies that we would also care about the timing of the "bigger picture"). If we can remove some of our timer classes, that would be great. Not suggesting that we forcibly prevent the use of Stopwatches/TImers in the codebase entirely -- just where it makes sense. > Consider consolidation of "timing" classes > -- > > Key: ACCUMULO-3329 > URL: https://issues.apache.org/jira/browse/ACCUMULO-3329 > Project: Accumulo > Issue Type: Improvement > Components: client, master, tserver >Reporter: Josh Elser > Labels: newbie > Fix For: 2.0.0 > > > We have a number of "timing" classes in or used by the codebase > * org.apache.accumulo.core.util.StopWatch > * org.apache.accumulo.core.util.OpTimer > * Traces > * Guava's Stopwatch > I'm assuming that consolidation of all of the timings into Traces would be > the best (assuming that if we care about the timing of a given operation > implies that twe would also care about the timing of the "bigger picture"). > If we can remove some of our timer classes, that would be great. Not > suggesting that we forcibly prevent the use of Stopwatches/TImers in the > codebase entirely -- just where it makes sense. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ACCUMULO-4718) Accumulo-testing classes are broken
[ https://issues.apache.org/jira/browse/ACCUMULO-4718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16199432#comment-16199432 ] Michael Miller commented on ACCUMULO-4718: -- The problem appears to be configuration related but is strange because some of the randomwalk tests work. It looks to just be Security.xml and Bulk.xml that are having problems connecting to Accumulo. > Accumulo-testing classes are broken > --- > > Key: ACCUMULO-4718 > URL: https://issues.apache.org/jira/browse/ACCUMULO-4718 > Project: Accumulo > Issue Type: Bug >Reporter: Michael Miller >Assignee: Michael Miller > Fix For: 2.0.0 > > > Multiple changes to 2.0 over the past 6 months or so have been left out of > the accumulo-testing repo. Update the testing classes with these changes so > they can be run against 2.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ACCUMULO-4718) Accumulo-testing classes are broken
[ https://issues.apache.org/jira/browse/ACCUMULO-4718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16199382#comment-16199382 ] Michael Miller commented on ACCUMULO-4718: -- Some of the randomwalk tests are broken. > Accumulo-testing classes are broken > --- > > Key: ACCUMULO-4718 > URL: https://issues.apache.org/jira/browse/ACCUMULO-4718 > Project: Accumulo > Issue Type: Bug >Reporter: Michael Miller >Assignee: Michael Miller > Fix For: 2.0.0 > > > Multiple changes to 2.0 over the past 6 months or so have been left out of > the accumulo-testing repo. Update the testing classes with these changes so > they can be run against 2.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Reopened] (ACCUMULO-4718) Accumulo-testing classes are broken
[ https://issues.apache.org/jira/browse/ACCUMULO-4718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Miller reopened ACCUMULO-4718: -- > Accumulo-testing classes are broken > --- > > Key: ACCUMULO-4718 > URL: https://issues.apache.org/jira/browse/ACCUMULO-4718 > Project: Accumulo > Issue Type: Bug >Reporter: Michael Miller >Assignee: Michael Miller > Fix For: 2.0.0 > > > Multiple changes to 2.0 over the past 6 months or so have been left out of > the accumulo-testing repo. Update the testing classes with these changes so > they can be run against 2.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (ACCUMULO-4591) Replication Latency Metrics2
[ https://issues.apache.org/jira/browse/ACCUMULO-4591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam J Shook reassigned ACCUMULO-4591: -- Assignee: Adam J Shook (was: Noe) > Replication Latency Metrics2 > > > Key: ACCUMULO-4591 > URL: https://issues.apache.org/jira/browse/ACCUMULO-4591 > Project: Accumulo > Issue Type: Improvement >Reporter: Noe >Assignee: Adam J Shook > Labels: pull-request-available > Fix For: 2.0.0 > > Attachments: Screen Shot 2017-02-23 at 9.31.06 AM.png > > Time Spent: 3h 40m > Remaining Estimate: 0h > > Currently Files Pending Replication is the only available insight to the > state of replication. Latency of replication has been a great concern. > Without a latency metric users can not determine what configuration settings > either reduce or increase replication latency. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ACCUMULO-4591) Replication Latency Metrics2
[ https://issues.apache.org/jira/browse/ACCUMULO-4591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated ACCUMULO-4591: - Labels: pull-request-available (was: ) > Replication Latency Metrics2 > > > Key: ACCUMULO-4591 > URL: https://issues.apache.org/jira/browse/ACCUMULO-4591 > Project: Accumulo > Issue Type: Improvement >Reporter: Noe >Assignee: Noe > Labels: pull-request-available > Fix For: 2.0.0 > > Attachments: Screen Shot 2017-02-23 at 9.31.06 AM.png > > Time Spent: 3.5h > Remaining Estimate: 0h > > Currently Files Pending Replication is the only available insight to the > state of replication. Latency of replication has been a great concern. > Without a latency metric users can not determine what configuration settings > either reduce or increase replication latency. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] adamjshook opened a new pull request #305: [ACCUMULO-4591] Add replication latency metrics
adamjshook opened a new pull request #305: [ACCUMULO-4591] Add replication latency metrics URL: https://github.com/apache/accumulo/pull/305 Supersedes #220 Trying to capture the latency based on WAL modification time and the current time once the file disappears from the status section of the replication table. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
