If there was an error happening during the service check, it will be in the 
Ambari agent logs.  I would look there first.

> On Feb 27, 2018, at 11:45 AM, Simon Elliston Ball 
> <si...@simonellistonball.com> wrote:
> 
> Anything appearing on the indexing topic in kafka? 
> 
> Anything in the logs for the indexing topology in Storm UI? 
> 
> Master isn’t always the best place to start, might be worth sticking to a 
> released build to kick the tyres. 
> 
> Simon
> 
>> On 27 Feb 2018, at 17:38, David McGinnis <mcginn...@avalonconsult.com> wrote:
>> 
>> All,
>> 
>> I have a kerberized HDP 2.6.3 cluster which I have installed Metron on 
>> through an MPack. I am using code straight from the master branch of the 
>> github as of last week. 
>> 
>> When I start Metron, all of the components correct start up. Shortly after, 
>> however, the Indexing Service stops working. I have not been able to find 
>> any logs that seem to capture any issues, and both indexing storm topologies 
>> are still active and running after the failure. Those topologies only report 
>> a warning about one of my parsers using the default HDFS writer config, 
>> which appears to be normal. 
>> 
>> Not only is this making my dashboard red when it shouldn't be, but also it 
>> seems as if data doesn't go through the pipeline until the entire Metron 
>> system is restarted. I am not confident this is related, but I suspect it 
>> is. 
>> 
>> Where should I go to find logs about this service, or does anyone have any 
>> ideas why this would be happening?
>> 
>> -- 
>> David McGinnis
>> Staff Hadoop Consultant | Avalon Consulting, LLC
>> M: (513) 439-0082
>> LinkedIn | Google+ | Twitter
>> -------------------------------------------------------------------------------------------------------------
>> This message (including any attachments) contains confidential information 
>> intended for a specific individual and purpose, and is protected by law. If 
>> you are not the intended recipient, you should delete this message. Any 
>> disclosure, copying, or distribution of this message, or the taking of any 
>> action based on it, is strictly prohibited.
> 

Reply via email to