mmiklavc commented on issue #1275: METRON-1878: Add Metron as a Knox service
URL: https://github.com/apache/metron/pull/1275#issuecomment-445979365
 
 
   > I will be looking into this further, but I see a lot of the following in 
the management UI logs. This repeated for more than 80k lines in a matter of 
minutes:
   > 
   > ```
   > 18/12/06 20:13:23 INFO zookeeper.ClientCnxn: Opening socket connection to 
server node1/192.168.66.121:2181. Will not attempt to authenticate using SASL 
(unknown error)
   > 18/12/06 20:13:23 WARN zookeeper.ClientCnxn: Session 0x1678019c6bb0099 for 
server null, unexpected error, closing socket connection and attempting 
reconnect
   > java.net.ConnectException: Connection refused
   >         at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
   >         at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
   >         at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:361)
   >         at 
org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1081)
   > 18/12/06 20:13:23 ERROR controller.RestExceptionHandler: Encountered 
error: Unable to get column metadata
   > org.apache.metron.rest.RestException: Unable to get column metadata
   >         at 
org.apache.metron.rest.service.impl.SearchServiceImpl.search(SearchServiceImpl.java:95)
   >         at 
org.apache.metron.rest.controller.SearchController.search(SearchController.java:54)
   >         at sun.reflect.GeneratedMethodAccessor239.invoke(Unknown Source)
   >         at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
   >         at java.lang.reflect.Method.invoke(Method.java:498)
   >         at 
org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:209)
   >         at 
org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:136)
   >         at 
org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:102)
   >         at 
org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:877)
   >         at 
org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:783)
   >         at 
org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:87)
   >         at 
org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:991)
   >         at 
org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:925)
   >         at 
org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:974)
   >         at 
org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:877)
   >         at javax.servlet.http.HttpServlet.service(HttpServlet.java:661)
   >         at 
org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:851)
   >         at javax.servlet.http.HttpServlet.service(HttpServlet.java:742)
   >         at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231)
   >         at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
   >         at 
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
   >         at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
   >         at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
   >         at 
   > ...
   > ```
   
   Turns out this was Zookeeper having gone down after HDFS filled up. Ambari 
had a lag in reporting. Independent of this PR, we might want to see about 
addressing REST api connectivity issues in the management UI. As it stands, the 
UI is left orphaned and inoperable without much explanation to the end user 
when something goes wrong when communicating with REST.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to