You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@metron.apache.org by mmiklavc <gi...@git.apache.org> on 2018/01/23 18:48:55 UTC

[GitHub] metron pull request #904: METRON-1400: Elasticsearch service check fails in ...

GitHub user mmiklavc opened a pull request:

    https://github.com/apache/metron/pull/904

    METRON-1400: Elasticsearch service check fails in Ambari

    ## Contributor Comments
    Addresses https://issues.apache.org/jira/browse/METRON-1400
    
    This file hasn't been touched since at least 2016, but the file=sys.stdout arg to the Logging statement is causing errors. I removed it and changed the ES host:port info to pull from the Ambari configs as we probably wanted all along. The regex is similar to what we did to setup links for ES health and indexes under ES Ambari Quicklinks.
    
    ## Testing
    
    ### Basic Test
    
    1. Spin up full dev
    2. Open Ambari at http://node1:8080
    3. Click on Elasticsearch in the service list
    4. Verify ES is running. Start it if it is not running.
    5. Click "Service Actions" and choose "Run Service Check" from the dropdown
    6. The service check should pass
    
    ### Check ES http port
    
    1. Click on Elasticsearch in the service list
    2. Select "Configs" in the tabs across the top of the page
    3. Enter "http_port" in the filter box
    4. Change the default "9200-9300" value to something else, e.g. "9700-9800"
    5. Click save and restart ES
    6. Once ES comes up again, click "Service Actions" and choose "Run Service Check" again from the dropdown
    7. The service check should still pass
    
    ## Pull Request Checklist
    
    ### For all changes:
    - [x] Is there a JIRA ticket associated with this PR? If not one needs to be created at [Metron Jira](https://issues.apache.org/jira/browse/METRON/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel). 
    - [x] Does your PR title start with METRON-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
    - [x] Has your PR been rebased against the latest commit within the target branch (typically master)?
    
    
    ### For code changes:
    - [x] Have you included steps to reproduce the behavior or problem that is being changed or addressed?
    - [x] Have you included steps or a guide to how the change may be verified and tested manually?
    - [x] Have you ensured that the full suite of tests and checks have been executed in the root metron folder via:
      ```
      mvn -q clean integration-test install && build_utils/verify_licenses.sh 
      ```
    
    - [x] Have you verified the basic functionality of the build by building and running locally with Vagrant full-dev environment or the equivalent?
    
    


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/mmiklavc/metron METRON-1400

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/metron/pull/904.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #904
    
----
commit 49aa0bb7c0c6b8ccc5fdbb58592a20c992b4579a
Author: Michael Miklavcic <mi...@...>
Date:   2018-01-23T18:34:34Z

    Elasticsearch service check fails in Ambari

----


---

[GitHub] metron issue #904: METRON-1400: Elasticsearch service check fails in Ambari

Posted by cestella <gi...@git.apache.org>.
Github user cestella commented on the issue:

    https://github.com/apache/metron/pull/904
  
    +1 by inspection, thanks!


---

[GitHub] metron issue #904: METRON-1400: Elasticsearch service check fails in Ambari

Posted by anandsubbu <gi...@git.apache.org>.
Github user anandsubbu commented on the issue:

    https://github.com/apache/metron/pull/904
  
    +1 works fine @mmiklavc .
    
    Verified on CentOS 7 multinode cluster. Simulated the problem first and then ran with the fix.
    
    Here is a sample output with the fix in place.
    
    ```
    2018-01-24 14:17:58,928 - Running Elastic search service check against metron-12.openstacklocal:9200
    2018-01-24 14:17:58,929 - Checking cluster health
    2018-01-24 14:17:58,929 - Execute['curl -sS -XGET 'http://metron-12.openstacklocal:9200/_cluster/health?wait_for_status=green&timeout=120s' | grep '"status":"green"''] {'logoutput': True, 'tries': 5, 'try_sleep': 10}
    {"cluster_name":"metron","status":"green","timed_out":false,"number_of_nodes":12,"number_of_data_nodes":11,"active_primary_shards":16,"active_shards":32,"relocating_shards":0,"initializing_shards":0,"unassigned_shards":0,"delayed_unassigned_shards":0,"number_of_pending_tasks":0,"number_of_in_flight_fetch":0,"task_max_waiting_in_queue_millis":0,"active_shards_percent_as_number":100.0}
    2018-01-24 14:17:58,967 - Elasticsearch service check successful
    
    Command completed successfully!
    
    ```


---

[GitHub] metron issue #904: METRON-1400: Elasticsearch service check fails in Ambari

Posted by mmiklavc <gi...@git.apache.org>.
Github user mmiklavc commented on the issue:

    https://github.com/apache/metron/pull/904
  
    Travis failure appears unrelated


---

[GitHub] metron pull request #904: METRON-1400: Elasticsearch service check fails in ...

Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:

    https://github.com/apache/metron/pull/904


---