I tried the code and it looks to be working.
On Sat, Oct 6, 2018 at 12:18 AM Lei Xia <[email protected]> wrote:
> Can you try the following code and see if it works? Thanks
>
> manager = HelixManagerFactory.getZKHelixManager(clusterName,
> instanceName,
> InstanceType.SPECTATOR, zkAddr);
>
> manager.connect();* routingTableProvider **= new
> RoutingTableProvider(manager);*
>
> List<InstanceConfig> list =
> routingTableProvider.getInstances("data2", "data2_0","MASTER");
>
>
> On Fri, Oct 5, 2018 at 4:07 PM Rob McKinnon <[email protected]>
> wrote:
>
>> Lei - I am using version 0.8.2
>>
>> On Fri, Oct 5, 2018 at 7:02 PM Lei Xia <[email protected]> wrote:
>>
>>> Hi, Rob
>>>
>>> Which helix version do you use? It seems there is a regression in
>>> our latest version, we will fix it asap. For now, you can workaround this
>>> bug by changing your code as follows, please give it a try and see if it
>>> works, thanks.
>>>
>>> manager = HelixManagerFactory.getZKHelixManager(clusterName, instanceName,
>>> InstanceType.SPECTATOR, zkAddr);
>>> zkAddress = zkAddr;
>>> helixClusterName = clusterName;
>>>
>>> manager.connect();* routingTableProvider **= new
>>> RoutingTableProvider(); ==> routingTableProvider = new
>>> RoutingTableProvider(manager);*
>>>
>>> manager.addExternalViewChangeListener(routingTableProvider);
>>>
>>>
>>>
>>> Thanks
>>> Lei
>>>
>>> On Tue, Oct 2, 2018 at 5:51 AM Rob McKinnon <[email protected]>
>>> wrote:
>>>
>>>> Lets say that I have a cluster of 5 nodes with 10 partitions and I have
>>>> an http request that needs to get data from a specific partition. What is
>>>> the pattern to make sure requests are routed to the correct node, in this
>>>> case a node that is the master of that particular partition?
>>>>
>>>> Regards,
>>>>
>>>> Rob
>>>>
>>>
>>>
>>> --
>>> Lei Xia
>>>
>>
>
> --
> Lei Xia
>
