Re: Configure Impala for Kudu on Separate Cluster

Todd, I'll keep this in mind. This information will be useful. I'll try again. Thanks, Ben On Wed, Aug 16, 2017 at 4:32 PM Todd Lipcon wrote: > On Wed, Aug 16, 2017 at 6:16 AM, Benjamin Kim wrote: > >> Hi, >> >> I found 2 issues. First, network

Re: Configure Impala for Kudu on Separate Cluster

Ben, As Todd mentioned, it might be some network connectivity problem. I would suspect some issues with connectivity between the node where the Impala shell is running and the Kudu master node. To start troubleshooting, I would verify that the node where you run the Impala shell (that's

Re: Configure Impala for Kudu on Separate Cluster

Todd, Caused by: org.apache.kudu.client.NoLeaderMasterFoundException: Master config (prod-dc1-datanode151.pdc1i.gradientx.com:7051) has no leader. Exceptions received: org.apache.kudu.client.RecoverableException: [Peer Kudu Master - prod-dc1-datanode151.pdc1i.gradientx.com:7051] Connection reset

Re: Configure Impala for Kudu on Separate Cluster

Todd, I'll check this with the systems team. Cheers, Ben On Mon, Aug 14, 2017 at 10:40 PM Todd Lipcon wrote: > Is there a possibility that the remote node (prod-dc1-datanode151) is > firewalled off from whatever host you are submitting the query to? The > error message is

Re: Configure Impala for Kudu on Separate Cluster

Is there a possibility that the remote node (prod-dc1-datanode151) is firewalled off from whatever host you are submitting the query to? The error message is admittedly pretty bad, but it basically means it's getting "connection refused", indicating that either there is no master running on that