[jira] [Commented] (ACCUMULO-4655) monitor should show response time in addition to last contact
[ https://issues.apache.org/jira/browse/ACCUMULO-4655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16102658#comment-16102658 ] Christopher Tubbs commented on ACCUMULO-4655: - Double-checked. This change has occurred after ACCUMULO-3005's work. So, this is completely done. > monitor should show response time in addition to last contact > - > > Key: ACCUMULO-4655 > URL: https://issues.apache.org/jira/browse/ACCUMULO-4655 > Project: Accumulo > Issue Type: New Feature > Components: monitor >Affects Versions: 1.6.6, 1.8.1 >Reporter: Ivan Bella >Assignee: Ivan Bella > Fix For: 1.8.2, 2.0.0 > > Time Spent: 4h > Remaining Estimate: 0h > > The monitor has a column for last contact. Sometimes that is due to a > tserver not responding. If we show the response time for a tserver to return > its status, then we would have the appropriate info. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ACCUMULO-4086) Allow configurable failsafe volume choosing
[
https://issues.apache.org/jira/browse/ACCUMULO-4086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16102654#comment-16102654
]
Christopher Tubbs commented on ACCUMULO-4086:
-
I've squashed all the changes from all the contributors, rebase'd onto master,
and updated the PR. I'd like to take one more look before the final merge,
though. There's some things I'm not quite sure about that I want to review
again. Additional eyes would also be appreciated.
> Allow configurable failsafe volume choosing
> ---
>
> Key: ACCUMULO-4086
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4086
> Project: Accumulo
> Issue Type: Sub-task
> Components: core
>Reporter: Christopher Tubbs
>Assignee: Christopher Tubbs
> Fix For: 2.0.0
>
> Time Spent: 4h 40m
> Remaining Estimate: 0h
>
> From parent issue:
> {quote}
> 3. In several places including {{PreferredVolumeChooser}},
> {{PerTableVolumeChooser}} and {{VolumeManagerImpl}}, the failsafe chooser is
> the {{RandomVolumeChooser}} which will include the instance volume that needs
> to be excluded. It would be useful to have a configurable failsafe in this
> situation.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ACCUMULO-4686) 1.8 upgrade path does not update version on multiple volumes
[ https://issues.apache.org/jira/browse/ACCUMULO-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Bella updated ACCUMULO-4686: - Fix Version/s: 1.7.4 > 1.8 upgrade path does not update version on multiple volumes > > > Key: ACCUMULO-4686 > URL: https://issues.apache.org/jira/browse/ACCUMULO-4686 > Project: Accumulo > Issue Type: Bug > Components: master >Affects Versions: 1.8.1 >Reporter: Ivan Bella >Assignee: Ivan Bella > Fix For: 1.7.4, 1.8.2, 2.0.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > The upgrade path from 1.6+ to 1.8 does not update the version across all > volumes in a multi-hdfs-volume cluster. Only one of them gets updated and > subsequently all of the tservers will complain and ultimately fail. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
