[jira] [Updated] (AMBARI-17031) Atlas Integration : Deploying HA Blueprint with Atlas does not work
[ https://issues.apache.org/jira/browse/AMBARI-17031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-17031: --- Attachment: AMBARI-17031-2.patch > Atlas Integration : Deploying HA Blueprint with Atlas does not work > --- > > Key: AMBARI-17031 > URL: https://issues.apache.org/jira/browse/AMBARI-17031 > Project: Ambari > Issue Type: Bug >Reporter: Tom Beerbower >Assignee: Tom Beerbower > Attachments: AMBARI-17031-2.patch > > > When deploying a blueprint that specified ha enabled > (atlas.server.ha.enabled=true), the atlas.server.address.id1, > atlas.server.address.id2 (etc) needs to be replaced with the hostnames for > the host group. This does not occur today, instead the > atlas.server.address.id1 is tokenized with (for example): > atlas.server.host.id1: "server_hosts", which is not quite correct. I believe > the blueprint runtime generator needs to create the proper entries with a > different token that is replaced with each host where Atlas server is > deployed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17031) Atlas Integration : Deploying HA Blueprint with Atlas does not work
[ https://issues.apache.org/jira/browse/AMBARI-17031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Beerbower updated AMBARI-17031: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Atlas Integration : Deploying HA Blueprint with Atlas does not work > --- > > Key: AMBARI-17031 > URL: https://issues.apache.org/jira/browse/AMBARI-17031 > Project: Ambari > Issue Type: Bug >Reporter: Tom Beerbower >Assignee: Tom Beerbower > > When deploying a blueprint that specified ha enabled > (atlas.server.ha.enabled=true), the atlas.server.address.id1, > atlas.server.address.id2 (etc) needs to be replaced with the hostnames for > the host group. This does not occur today, instead the > atlas.server.address.id1 is tokenized with (for example): > atlas.server.host.id1: "server_hosts", which is not quite correct. I believe > the blueprint runtime generator needs to create the proper entries with a > different token that is replaced with each host where Atlas server is > deployed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17031) Atlas Integration : Deploying HA Blueprint with Atlas does not work
[ https://issues.apache.org/jira/browse/AMBARI-17031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Beerbower updated AMBARI-17031: --- Status: Patch Available (was: In Progress) > Atlas Integration : Deploying HA Blueprint with Atlas does not work > --- > > Key: AMBARI-17031 > URL: https://issues.apache.org/jira/browse/AMBARI-17031 > Project: Ambari > Issue Type: Bug >Reporter: Tom Beerbower >Assignee: Tom Beerbower > Attachments: AMBARI-17031.patch > > > When deploying a blueprint that specified ha enabled > (atlas.server.ha.enabled=true), the atlas.server.address.id1, > atlas.server.address.id2 (etc) needs to be replaced with the hostnames for > the host group. This does not occur today, instead the > atlas.server.address.id1 is tokenized with (for example): > atlas.server.host.id1: "server_hosts", which is not quite correct. I believe > the blueprint runtime generator needs to create the proper entries with a > different token that is replaced with each host where Atlas server is > deployed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17031) Atlas Integration : Deploying HA Blueprint with Atlas does not work
[ https://issues.apache.org/jira/browse/AMBARI-17031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Beerbower updated AMBARI-17031: --- Attachment: AMBARI-17031.patch > Atlas Integration : Deploying HA Blueprint with Atlas does not work > --- > > Key: AMBARI-17031 > URL: https://issues.apache.org/jira/browse/AMBARI-17031 > Project: Ambari > Issue Type: Bug >Reporter: Tom Beerbower >Assignee: Tom Beerbower > Attachments: AMBARI-17031.patch > > > When deploying a blueprint that specified ha enabled > (atlas.server.ha.enabled=true), the atlas.server.address.id1, > atlas.server.address.id2 (etc) needs to be replaced with the hostnames for > the host group. This does not occur today, instead the > atlas.server.address.id1 is tokenized with (for example): > atlas.server.host.id1: "server_hosts", which is not quite correct. I believe > the blueprint runtime generator needs to create the proper entries with a > different token that is replaced with each host where Atlas server is > deployed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
