[
https://issues.apache.org/jira/browse/HBASE-6617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14709694#comment-14709694
]
Yu Li commented on HBASE-6617:
------------------------------
Could you further explain where the incompatibility lies? I guess you mean the
change in ClusterStatus.proto? I think the groupId would be necessary for
monitoring to show so I added it as an *optional* field, and IMHO this won't
involve incompatibility
> ReplicationSourceManager should be able to track multiple WAL paths
> -------------------------------------------------------------------
>
> Key: HBASE-6617
> URL: https://issues.apache.org/jira/browse/HBASE-6617
> Project: HBase
> Issue Type: Improvement
> Components: Replication
> Reporter: Ted Yu
> Assignee: Sean Busbey
> Fix For: 2.0.0, 1.3.0
>
> Attachments: HBASE-6617.patch
>
>
> Currently ReplicationSourceManager uses logRolled() to receive notification
> about new HLog and remembers it in latestPath.
> When region server has multiple WAL support, we need to keep track of
> multiple Path's in ReplicationSourceManager
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
