hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jesse Yates (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-11497) Expose RpcScheduling implementations as Public Interfaces
Date Thu, 10 Jul 2014 19:24:04 GMT

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

Jesse Yates updated HBASE-11497:
--------------------------------

    Description: 
In PHOENIX-938 we are attempting to resolve cross-RS deadlocks in indexing by adding custom
RPC handlers (so regular puts/reads don't interfere with index updates). However, we've run
into a couple of snags where the interfaces change, making it a bit more difficult to support
interoperability between minor versions as the underlying RPC handling changed (for the better,
but still different :).

This would just mark those interfaces Public, Evolving, so we still have some flexibility,
but don't break existing usage.

Note, this kind of thing will come up for any client who is doing custom RPC handling - beyond
the recently added flexibility - but wants to stay in line with the current HBase implementation
(rather than building their own RPC handling mechanisms).

  was:
In Phoenix-938 we are attempting to resolve cross-RS deadlocks in indexing by adding custom
RPC handlers (so regular puts/reads don't interfere with index updates). However, we've run
into a couple of snags where the interfaces change, making it a bit more difficult to support
interoperability between minor versions as the underlying RPC handling changed (for the better,
but still different :).

This would just mark those interfaces Public, Evolving, so we still have some flexibility,
but don't break existing usage.

Note, this kind of thing will come up for any client who is doing custom RPC handling - beyond
the recently added flexibility - but wants to stay in line with the current HBase implementation
(rather than building their own RPC handling mechanisms).


> Expose RpcScheduling implementations as Public Interfaces
> ---------------------------------------------------------
>
>                 Key: HBASE-11497
>                 URL: https://issues.apache.org/jira/browse/HBASE-11497
>             Project: HBase
>          Issue Type: Improvement
>          Components: io, regionserver, Usability
>    Affects Versions: 0.99.0, 0.98.4
>            Reporter: Jesse Yates
>
> In PHOENIX-938 we are attempting to resolve cross-RS deadlocks in indexing by adding
custom RPC handlers (so regular puts/reads don't interfere with index updates). However, we've
run into a couple of snags where the interfaces change, making it a bit more difficult to
support interoperability between minor versions as the underlying RPC handling changed (for
the better, but still different :).
> This would just mark those interfaces Public, Evolving, so we still have some flexibility,
but don't break existing usage.
> Note, this kind of thing will come up for any client who is doing custom RPC handling
- beyond the recently added flexibility - but wants to stay in line with the current HBase
implementation (rather than building their own RPC handling mechanisms).



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message