[jira] [Resolved] (GEODE-1936) ClientMetadata::getServerLocation is returning a primary BucketServerLocationPtr instead of a secondary

["Charlie Black (JIRA)" <ji...@apache.org>]

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

Charlie Black resolved GEODE-1936.
----------------------------------
       Resolution: Won't Fix
    Fix Version/s: 1.8.0

tryPrimary - if the argument is true the code will return the primary otherwise it will give a random server that is hosting the bucket.   If you are looking for more info on primaries or secondaries please review the ClientMetadata::adviseServerLocations method.   That method will return a vector of servers that is hosting the data.    There you can inquire if the server if it is primary or secondary.

I will be closing this Jira as won't fix since the intent of the API wasn't to return a secondary if try primary was false.

> ClientMetadata::getServerLocation is returning a primary BucketServerLocationPtr instead of a secondary
> -------------------------------------------------------------------------------------------------------
>
>                 Key: GEODE-1936
>                 URL: https://issues.apache.org/jira/browse/GEODE-1936
>             Project: Geode
>          Issue Type: Bug
>          Components: native client
>            Reporter: Daniel Farcovich
>            Assignee: Jacob S. Barrett
>            Priority: Major
>             Fix For: 1.8.0
>
>
> In the cpp client code geode-client-native\src\cppcache\impl\ClientMetadata.cpp  a pointer to a primary BucketServerLocationPtr can be returned when asking for a secondary. The returned BucketServerLocationPtr is a randomization between [0, m_bucketServerLocationsList[bucketId].size()-1] where the result can be a primary copy.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)