accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ACCUMULO-1259) ShutdownTServer FATE step's call() method sits in a loop: should use isReady() instead
Date Tue, 03 Mar 2015 17:23:04 GMT

     [ https://issues.apache.org/jira/browse/ACCUMULO-1259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Josh Elser updated ACCUMULO-1259:
---------------------------------
    Attachment: 0001-ACCUMULO-1259-Wait-asynchronously-for-TServer-to-go-.patch

Updated patch based on [~vickyuec]'s original patch. Changes I made:

* Original patch didn't cleanly apply against master, applied it by hand.
* Ensures that the force option doesn't wait
* Removes the ShutdownTServerWait class
* Requests that the master only shutdown the tserver once (not repeatedly)
* Doesn't wait if null connection to server is returned (prevent an extra call to {{isReady()}})

> ShutdownTServer FATE step's call() method sits in a loop: should use isReady() instead
> --------------------------------------------------------------------------------------
>
>                 Key: ACCUMULO-1259
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1259
>             Project: Accumulo
>          Issue Type: Bug
>            Reporter: Eric Newton
>            Assignee: Vikram Srivastava
>            Priority: Critical
>             Fix For: 1.7.0
>
>         Attachments: 0001-ACCUMULO-1259-Wait-asynchronously-for-TServer-to-go-.patch,
ACCUMULO-1259.v1.patch.txt
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message