[AMBARI-17662] Atlas HA fails to come up with error finding ids

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.4.0
• Fix Version/s: 2.4.0
• Component/s: stacks
• Assignee: Alejandro Fernandez
• Reporter: Alejandro Fernandez
• Created: 11/Jul/16 21:27
• Updated: 13/Jul/16 00:04
• Resolved: 12/Jul/16 20:46

Description

Deploy multiple Atlas servers and one of them will fail since it will be missing its ids.

2016-06-14 10:48:23,249 WARN  - [main:] ~ Failed startup of context o.e.j.w.WebAppContext@2ad31d76{/,file:/grid/0/hdp/2.5.0.0-723/atlas/server/webapp/atlas/,STARTING}{/usr/hdp/current/atlas-server/server/webapp/atlas} (WebAppContext:514)
java.lang.RuntimeException: org.apache.atlas.AtlasException: Could not find server id for this instance. Unable to find IDs matching any local host and port binding among id1
        at org.apache.atlas.service.Services.start(Services.java:48)
        at org.apache.atlas.web.listeners.GuiceServletConfig.startServices(GuiceServletConfig.java:142)
        at org.apache.atlas.web.listeners.GuiceServletConfig.contextInitialized(GuiceServletConfig.java:136)
        at org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:800)
        at org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:444)
        at org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:791)
        at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:294)
        at org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1349)
        at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1342)
        at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:741)
        at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:505)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
        at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
        at org.eclipse.jetty.server.Server.start(Server.java:387)
        at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
        at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
        at org.eclipse.jetty.server.Server.doStart(Server.java:354)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
        at org.apache.atlas.web.service.EmbeddedServer.start(EmbeddedServer.java:93)
        at org.apache.atlas.Atlas.main(Atlas.java:113)
Caused by: org.apache.atlas.AtlasException: Could not find server id for this instance. Unable to find IDs matching any local host and port binding among id1
        at org.apache.atlas.ha.AtlasServerIdSelector.selectServerId(AtlasServerIdSelector.java:77)
        at org.apache.atlas.web.service.ActiveInstanceElectorService.start(ActiveInstanceElectorService.java:105)
        at org.apache.atlas.service.Services.start(Services.java:45)
        ... 19 more
2016-06-14 10:48:23,284 INFO  - [main:] ~ Started ServerConnector@255af999{HTTP/1.1}{0.0.0.0:21000} (ServerConnector:266)

To fix this,

atlas.server.ha.enabled will not be shown on the UI and instead derived. But if for whatever reason we need to do some debugging/troubleshooting on Atlas, we may allow the user to override the property.

• single Atlas Server => write config with atlas.server.ha.enabled=false (if atlas.server.ha.enabled is set to true, still write it out as false)
• multiple Atlas Servers => write config with atlas.server.ha.enabled=true (only if atlas.server.ha.enabled is not a property, otherwise, take its value)

Issue Links

• relates to: AMBARI-17273 With Atlas HA enabled, atlas instance fails to come up with "Unable to find IDs matching any local host and port binding among id1"
• links to: Review Board patch