You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2016/12/12 03:13:58 UTC
[jira] [Resolved] (KUDU-1776) 'kudu remote_replica copy' ends up
fetching wildcard address from source server
[ https://issues.apache.org/jira/browse/KUDU-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Todd Lipcon resolved KUDU-1776.
-------------------------------
Resolution: Fixed
Fix Version/s: 1.2.0
> 'kudu remote_replica copy' ends up fetching wildcard address from source server
> -------------------------------------------------------------------------------
>
> Key: KUDU-1776
> URL: https://issues.apache.org/jira/browse/KUDU-1776
> Project: Kudu
> Issue Type: Bug
> Components: ops-tooling
> Affects Versions: 1.1.0
> Reporter: Todd Lipcon
> Assignee: Dinesh Bhat
> Priority: Critical
> Fix For: 1.2.0
>
>
> 'remote_replica copy' seems to ask the source server for its bound address, but that address is likely to be a wildcard in a real cluster. It then sends a faulty request like:
> {code}
> tablet_id: "834e7673f32e4802bdf26f9fff9162ef"
> copy_peer_uuid: "893679e1b1dd4342bf1fb8f058ec2789"
> copy_peer_addr {
> host: "0.0.0.0"
> port: 7050
> }
> {code}
> resulting in: UNKNOWN_ERROR: Invalid wildcard address to tablet copy from: 0.0.0.0 (resolved to 0.0.0.0)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)