[jira] [Resolved] (ACCUMULO-4061) Add way to determine Accumulo version from a running tserver
[ https://issues.apache.org/jira/browse/ACCUMULO-4061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher Tubbs resolved ACCUMULO-4061. - Resolution: Fixed > Add way to determine Accumulo version from a running tserver > > > Key: ACCUMULO-4061 > URL: https://issues.apache.org/jira/browse/ACCUMULO-4061 > Project: Accumulo > Issue Type: New Feature > Components: tserver >Reporter: Ed Coleman >Assignee: Luis Tavarez >Priority: Minor > Fix For: 2.0.0 > > Time Spent: 1.5h > Remaining Estimate: 0h > > When upgrading by performing a rolling restart, realized that there was no > way to determine the version of a running tserver other than using ps to get > start time or maybe a versioned package on the classpath. > A typical deployment structure seems to be lay down the Accumulo directories > with a version and then use a symbolic link to point to the version that is > used at run-time. As an example: > /usr/local/accumulo > /usr/local/accumulo/accumulo-1.6.2 > /usr/local/accumulo/accumulo-1.6.3 > /usr/local/accumulo/accumulo-latest --> /usr/local/accumulo/accumulo-1.6.3 > To upgrade without a complete shutdown, we lay down the new version, update > the symbolic link and then perform a rolling restart of the tservers, with > scripts, env,... using the symbolic link to specify which version are used. > Realized that if the rolling shutdown failed for any particular tserver, it > would keep running the previous version. The only way to determine if we > were running the desired version was to use ps and check the running time of > the tserver process. > The could also be a situation were a "dead" server would be offline during > the upgrade and not receive the new version. If the server was resurrected > and services started before updated versions are installed it could be > difficult to determine exactly what version of the tserver was running. > It would be nice if there was some way to ask a running tserver what version > it is. That way, post-upgrade we could confirm that all running tservers > reply with the expected version. -- 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=16099253#comment-16099253
]
Christopher Tubbs commented on ACCUMULO-4086:
-
Yes, I'd like to close this one out also. I would like to take another look at
it tomorrow before merging myself, but if you want to wrap it up before then,
feel free to do that.
> 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] [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=16099197#comment-16099197
]
Ivan Bella commented on ACCUMULO-4086:
--
I am needing this change for deployment onto our test system. Can we attempt
to get this one wrapped up? I see there are now conflicts that have crept in.
I will attempt to resolve those with another pull request into your branch.
> 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] [Resolved] (ACCUMULO-4685) Fix minor warnings
[ https://issues.apache.org/jira/browse/ACCUMULO-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher Tubbs resolved ACCUMULO-4685. - Resolution: Fixed > Fix minor warnings > -- > > Key: ACCUMULO-4685 > URL: https://issues.apache.org/jira/browse/ACCUMULO-4685 > Project: Accumulo > Issue Type: Bug >Reporter: Christopher Tubbs >Assignee: Christopher Tubbs >Priority: Minor > Fix For: 1.7.4, 1.8.2, 2.0.0 > > Time Spent: 1h > Remaining Estimate: 0h > > Fix minor compiler warnings. Mostly type safety issues from lack of proper > use of generics. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ACCUMULO-4685) Fix minor warnings
[ https://issues.apache.org/jira/browse/ACCUMULO-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher Tubbs updated ACCUMULO-4685: Description: Fix minor compiler warnings. Mostly type safety issues from lack of proper use of generics. > Fix minor warnings > -- > > Key: ACCUMULO-4685 > URL: https://issues.apache.org/jira/browse/ACCUMULO-4685 > Project: Accumulo > Issue Type: Bug >Reporter: Christopher Tubbs >Assignee: Christopher Tubbs >Priority: Minor > Fix For: 1.7.4, 1.8.2, 2.0.0 > > Time Spent: 1h > Remaining Estimate: 0h > > Fix minor compiler warnings. Mostly type safety issues from lack of proper > use of generics. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ACCUMULO-4685) Fix minor warnings
[ https://issues.apache.org/jira/browse/ACCUMULO-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob updated ACCUMULO-4685: Priority: Minor (was: Major) > Fix minor warnings > -- > > Key: ACCUMULO-4685 > URL: https://issues.apache.org/jira/browse/ACCUMULO-4685 > Project: Accumulo > Issue Type: Bug >Reporter: Christopher Tubbs >Assignee: Christopher Tubbs >Priority: Minor > Fix For: 1.7.4, 1.8.2, 2.0.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ACCUMULO-4685) Fix minor warnings
Christopher Tubbs created ACCUMULO-4685: --- Summary: Fix minor warnings Key: ACCUMULO-4685 URL: https://issues.apache.org/jira/browse/ACCUMULO-4685 Project: Accumulo Issue Type: Bug Reporter: Christopher Tubbs Assignee: Christopher Tubbs Fix For: 1.7.4, 1.8.2, 2.0.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ACCUMULO-4684) Add replication table schema to docs
[ https://issues.apache.org/jira/browse/ACCUMULO-4684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser updated ACCUMULO-4684: - Attachment: ACCUMULO-4684.001.patch .001 Here's what I remember, merged with ReplicationSchema. I'll let Adam validate me ;) > Add replication table schema to docs > > > Key: ACCUMULO-4684 > URL: https://issues.apache.org/jira/browse/ACCUMULO-4684 > Project: Accumulo > Issue Type: Task > Components: docs >Reporter: Josh Elser >Assignee: Josh Elser >Priority: Minor > Fix For: 1.7.4, 1.8.2, 2.0.0 > > Attachments: ACCUMULO-4684.001.patch > > > I keep going to our documentation to find what the replication table looks > like, but am disappointed when I remember that I never wrote such docs. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ACCUMULO-4684) Add replication table schema to docs
[ https://issues.apache.org/jira/browse/ACCUMULO-4684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16099003#comment-16099003 ] Josh Elser commented on ACCUMULO-4684: -- Awesome! The more info the better. I've started pulling the info from ReplicationSchema.java into asciidoc. I'm sure you have some useful stuff we can also put in with that. > Add replication table schema to docs > > > Key: ACCUMULO-4684 > URL: https://issues.apache.org/jira/browse/ACCUMULO-4684 > Project: Accumulo > Issue Type: Task > Components: docs >Reporter: Josh Elser >Assignee: Josh Elser >Priority: Minor > Fix For: 1.7.4, 1.8.2, 2.0.0 > > > I keep going to our documentation to find what the replication table looks > like, but am disappointed when I remember that I never wrote such docs. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ACCUMULO-4684) Add replication table schema to docs
[ https://issues.apache.org/jira/browse/ACCUMULO-4684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16098993#comment-16098993 ] Adam J Shook commented on ACCUMULO-4684: I actually have a fairly detailed document about how the replication system works, including some details on the replication table. I'll need to check it and scrub it of any IP but I don't see a problem sharing it to help with this ticket -- just give me a couple days to double check! > Add replication table schema to docs > > > Key: ACCUMULO-4684 > URL: https://issues.apache.org/jira/browse/ACCUMULO-4684 > Project: Accumulo > Issue Type: Task > Components: docs >Reporter: Josh Elser >Assignee: Josh Elser >Priority: Minor > Fix For: 1.7.4, 1.8.2, 2.0.0 > > > I keep going to our documentation to find what the replication table looks > like, but am disappointed when I remember that I never wrote such docs. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ACCUMULO-4684) Add replication table schema to docs
Josh Elser created ACCUMULO-4684: Summary: Add replication table schema to docs Key: ACCUMULO-4684 URL: https://issues.apache.org/jira/browse/ACCUMULO-4684 Project: Accumulo Issue Type: Task Components: docs Reporter: Josh Elser Assignee: Josh Elser Priority: Minor Fix For: 1.7.4, 1.8.2, 2.0.0 I keep going to our documentation to find what the replication table looks like, but am disappointed when I remember that I never wrote such docs. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ACCUMULO-4683) Create IT for monitor REST endpoints
Christopher Tubbs created ACCUMULO-4683: --- Summary: Create IT for monitor REST endpoints Key: ACCUMULO-4683 URL: https://issues.apache.org/jira/browse/ACCUMULO-4683 Project: Accumulo Issue Type: Test Components: monitor Reporter: Christopher Tubbs Fix For: 2.0.0 With the changes to the monitor in ACCUMULO-3005, it'd be nice to have an integration test to verify the REST endpoints as API. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
