accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Newton (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-3805) No means to monitor/interact with FATE programmatically
Date Thu, 14 May 2015 19:41:00 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-3805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544247#comment-14544247
] 

Eric Newton commented on ACCUMULO-3805:
---------------------------------------

Brainstorming ideas:

* expose the FATE component steps:
** initiate the transaction
** get the result, with timeout
** add calls to get status
* augment the status with:
** started / waiting
** running / ready
** last update time
** identity of the requester
* add an API to fetch the transactions and their status




> No means to monitor/interact with FATE programmatically
> -------------------------------------------------------
>
>                 Key: ACCUMULO-3805
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3805
>             Project: Accumulo
>          Issue Type: Bug
>          Components: fate
>            Reporter: John Vines
>
> With FATE, we have the ability to have strong tracking of operations. However, we hide
a lot of this from the client. We have admin utilities plumbed into the shell (FateCommand),
but they're not actual APIs. This means there is no API available for failing/deleting/listing
fate operations, but it also means there no way to be aware of the txid for a fate operation.
This is critical for instances where a potentially distributed client wants to perform a FATEd
operation.
> In an ideal world, client would be able to pre-seed the transaction, as we do now, and
then issue the command with that id. This would allow the client to be aware of the transaction
before it's started so it could be shared.



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

Mime
View raw message