Agreed. On Feb 15, 2018 11:39 AM, "Phil Zampino (JIRA)" <j...@apache.org> wrote:
> > [ https://issues.apache.org/jira/browse/KNOX-1184?page= > com.atlassian.jira.plugin.system.issuetabpanels:comment- > tabpanel&focusedCommentId=16365867#comment-16365867 ] > > Phil Zampino commented on KNOX-1184: > ------------------------------------ > > In my opinion, the service discovery is correctly determining the Atlas > host endpoints, and I believe the appropriate solution to this issue is > actually to implement proper HA support for Atlas in Knox. > > In the meantime, the work-around for this is to populate the Atlas service > declaration in the descriptor with the active URL to override the endpoint > discovery in the generated topology. > > > [Service Discovery] Atlas endpoint url is not updated properly in the > generated topology > > ------------------------------------------------------------ > ---------------------------- > > > > Key: KNOX-1184 > > URL: https://issues.apache.org/jira/browse/KNOX-1184 > > Project: Apache Knox > > Issue Type: Bug > > Affects Versions: 0.14.0 > > Environment: knox proxy and service discovery enabled > > Reporter: J.Andreina > > Assignee: Phil Zampino > > Priority: Major > > Fix For: 1.1.0 > > > > > > Service discovery: > > Verified knox proxy feature through the generated topology file from > service discovery feature > > *Expectation:* > > *=========* > > Generated topology file should have only the active atlas endpoint url , > as HaProvider for atlas is not yet supported > > when we access atlas through knox proxy, should'nt expose the atlas ip > and port information. > > {color:#FF0000}*Actual:*{color} > > {color:#FF0000}*=====*{color} > > Generated topology has both passive and active url for "ATLAS" service > and passive url for "ATLAS-API" service. > > Hence accessing atlas through knox proxy redirects me to the atlas > active endpoint url, hence knox proxy fails. > > Explained the failure case in scenario 1 below > > Environment: > > ============ > > Atlas has 2 host > > host1 - acive_host > > host2 - passive_host > > {color:red}Scenario 1: > > ==========={color} > > Generated topology using service discovery feature > > {noformat} > > <service> > > <role>ATLAS</role> > > <url>http://{color:#FF0000}host2{color}:21000</url> > > <url>http://host1:21000</url> > > </service> > > <service> > > <role>ATLAS-API</role> > > <url>http://{color:#FF0000}host2{color}:21000</url> > > </service> > > {noformat} > > Here accessing the atlas through knox proxy redirects me to active atlas > host1 url > > {color:#d04437}accessing url : https://<gateway-host>:8443/ > gateway/ui/atlas > > redirected url : http:/host1:21000/login.jsp{color} > > {color:#14892c}Scenario 2: > > =============={color} > > when i manually modified the atlas endpoint to only active url in > generated topology file then the knox proxy works fine > > {noformat} > > </gateway> > > <service> > > <role>ATLAS</role> > > <url>http://host1:21000</url> > > </service> > > <service> > > <role>ATLAS-API</role> > > <url>http://host1:21000</url> > > </service> > > {noformat} > > {color:#14892c}accessing url : https://gateway-host:8443/ > gateway/ui/atlas > > redirected url: https://gateway-host:8443/gateway/ui/atlas/login.jsp{ > color} > > > > -- > This message was sent by Atlassian JIRA > (v7.6.3#76005) >
