[jira] [Created] (METRON-1484) Indexing Topologies Fail Partial Start in Ambari
Michael Miklavcic created METRON-1484: - Summary: Indexing Topologies Fail Partial Start in Ambari Key: METRON-1484 URL: https://issues.apache.org/jira/browse/METRON-1484 Project: Metron Issue Type: Bug Reporter: Michael Miklavcic If either topology is down, Ambari shows all of Indexing as dead. Clicking start attempts to start them both and fails if either is still running. Furthermore, it appears to retry 3 times before finally failing the command. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (METRON-1471) Migrate shuffle connections to local or shuffle
[ https://issues.apache.org/jira/browse/METRON-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16392000#comment-16392000 ] ASF GitHub Bot commented on METRON-1471: Github user asfgit closed the pull request at: https://github.com/apache/metron/pull/949 > Migrate shuffle connections to local or shuffle > --- > > Key: METRON-1471 > URL: https://issues.apache.org/jira/browse/METRON-1471 > Project: Metron > Issue Type: Improvement >Reporter: Casey Stella >Priority: Major > > Currently, we use shuffle groupings when we do not want to group by field. > We should, instead, use local or shuffle groupings. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (METRON-1482) Update REST to work with Solr
[ https://issues.apache.org/jira/browse/METRON-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391860#comment-16391860 ] ASF GitHub Bot commented on METRON-1482: Github user merrimanr closed the pull request at: https://github.com/apache/metron/pull/957 > Update REST to work with Solr > - > > Key: METRON-1482 > URL: https://issues.apache.org/jira/browse/METRON-1482 > Project: Metron > Issue Type: Sub-task >Reporter: Ryan Merriman >Assignee: Ryan Merriman >Priority: Major > > Ambari should start REST with the correct Solr indexing jar on the classpath. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (METRON-1464) Convert schemas to be compatible with Solr 5.5.2
[ https://issues.apache.org/jira/browse/METRON-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391858#comment-16391858 ] ASF GitHub Bot commented on METRON-1464: Github user merrimanr closed the pull request at: https://github.com/apache/metron/pull/945 > Convert schemas to be compatible with Solr 5.5.2 > > > Key: METRON-1464 > URL: https://issues.apache.org/jira/browse/METRON-1464 > Project: Metron > Issue Type: Sub-task >Reporter: Ryan Merriman >Assignee: Ryan Merriman >Priority: Major > > It would be ideal if our Solr schemas were compatible with Solr 5.5.2 or > 6.6.2. This would be users the option of using a manually installed Solr or > HDP Search. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (METRON-1483) Create a tool to monitor performance of the topologies
[ https://issues.apache.org/jira/browse/METRON-1483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391819#comment-16391819 ] ASF GitHub Bot commented on METRON-1483: Github user cestella commented on the issue: https://github.com/apache/metron/pull/958 # Testing Plan: We presume * `ZOOKEEPER` is an environment variable set to the zk quorum (e.g. `node1:2181`) * `BROKER` is an environment variable set to the broker (e.g. `node1:6667`) ## Unbiased Generation In order to test this, we will: 1. create a new topic ``` # Create dummy_12_unbiased with 12 partitions /usr/hdp/current/kafka-broker/bin/kafka-topics.sh --zookeeper $ZOOKEEPER --create --topic dummy_12_unbiased --partitions 12 --replication-factor 1 ``` 2. Create some dummy data to send into kafka ``` # Generate some templates of dummy data that look like CSV in ~/dummy.templates # With a number, a string, a GUID and the timestamp for i in $(seq 1 100);do echo "$i,foo,\$METRON_GUID,\$METRON_TS";done > ~/dummy.templates ``` 3. Write into that topic from a set of templates at a specified rate ``` # Write out 1000 messages per second to dummy_12_unbiased # Monitor dummy_12_unbiased # Each message is drawn from the set of templates in step 2. # Stop after 60 seconds and report how much you've written $METRON_HOME/bin/load_tool.sh -p 5 -ot dummy_12_unbiased -mt dummy_12_unbiased -t ~/dummy.template -eps 1000 -z $ZOOKEEPER -tl 6 ``` * It should indicate that it generated something like 60k messages 4. Measure if the messages generated roughly match the requested rate. ``` # You will have to ctrl-c this in a few seconds /usr/hdp/current/kafka-broker/bin/kafka-console-consumer.sh --bootstrap-server node1:6667 --topic dummy_12_topic --from-beginning | wc -l ``` * It should output something like `Processed a total of 60400 messages`, which would be about 1000 messages per second. > Create a tool to monitor performance of the topologies > -- > > Key: METRON-1483 > URL: https://issues.apache.org/jira/browse/METRON-1483 > Project: Metron > Issue Type: New Feature >Reporter: Casey Stella >Priority: Major > > In performance evaluation, generating synthetic load and monitoring the write > throughput of our kafka-to-kafka topologies has required a lot of custom > scripting. We should have a tool that could do the following: > * Take a file representing a message template and generate synthetic load at > a given events per second > * Monitor the kafka offsets of a topic and report throughput numbers in > events per second > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (METRON-1471) Migrate shuffle connections to local or shuffle
[ https://issues.apache.org/jira/browse/METRON-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391598#comment-16391598 ] ASF GitHub Bot commented on METRON-1471: Github user merrimanr commented on the issue: https://github.com/apache/metron/pull/949 +1 thanks! > Migrate shuffle connections to local or shuffle > --- > > Key: METRON-1471 > URL: https://issues.apache.org/jira/browse/METRON-1471 > Project: Metron > Issue Type: Improvement >Reporter: Casey Stella >Priority: Major > > Currently, we use shuffle groupings when we do not want to group by field. > We should, instead, use local or shuffle groupings. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (METRON-1482) Update REST to work with Solr
[ https://issues.apache.org/jira/browse/METRON-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391589#comment-16391589 ] ASF GitHub Bot commented on METRON-1482: Github user justinleet commented on the issue: https://github.com/apache/metron/pull/957 +1, I'm able to spin it up and query. Good job! > Update REST to work with Solr > - > > Key: METRON-1482 > URL: https://issues.apache.org/jira/browse/METRON-1482 > Project: Metron > Issue Type: Sub-task >Reporter: Ryan Merriman >Assignee: Ryan Merriman >Priority: Major > > Ambari should start REST with the correct Solr indexing jar on the classpath. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (METRON-1482) Update REST to work with Solr
[ https://issues.apache.org/jira/browse/METRON-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391571#comment-16391571 ] ASF GitHub Bot commented on METRON-1482: Github user justinleet commented on the issue: https://github.com/apache/metron/pull/957 Don't leave an extra square brace. Sigh. My bad > Update REST to work with Solr > - > > Key: METRON-1482 > URL: https://issues.apache.org/jira/browse/METRON-1482 > Project: Metron > Issue Type: Sub-task >Reporter: Ryan Merriman >Assignee: Ryan Merriman >Priority: Major > > Ambari should start REST with the correct Solr indexing jar on the classpath. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (METRON-1482) Update REST to work with Solr
[ https://issues.apache.org/jira/browse/METRON-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391542#comment-16391542 ] ASF GitHub Bot commented on METRON-1482: Github user justinleet commented on the issue: https://github.com/apache/metron/pull/957 Error code is just a 400, btw. > Update REST to work with Solr > - > > Key: METRON-1482 > URL: https://issues.apache.org/jira/browse/METRON-1482 > Project: Metron > Issue Type: Sub-task >Reporter: Ryan Merriman >Assignee: Ryan Merriman >Priority: Major > > Ambari should start REST with the correct Solr indexing jar on the classpath. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (METRON-1482) Update REST to work with Solr
[
https://issues.apache.org/jira/browse/METRON-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391541#comment-16391541
]
ASF GitHub Bot commented on METRON-1482:
Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/957
I'm unable to get a fairly basic query working. A matching doc exists,
based on querying solr directly. I assume I'm doing something obviously wrong
here?
```
{
"fields": [
"*"
],
"from": 0,
"indices": [
"bro"
],
"query": "adapter.threatinteladapter.end.ts:1520528353609"
]
}
```
> Update REST to work with Solr
> -
>
> Key: METRON-1482
> URL: https://issues.apache.org/jira/browse/METRON-1482
> Project: Metron
> Issue Type: Sub-task
>Reporter: Ryan Merriman
>Assignee: Ryan Merriman
>Priority: Major
>
> Ambari should start REST with the correct Solr indexing jar on the classpath.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (METRON-1471) Migrate shuffle connections to local or shuffle
[ https://issues.apache.org/jira/browse/METRON-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391506#comment-16391506 ] ASF GitHub Bot commented on METRON-1471: Github user cestella closed the pull request at: https://github.com/apache/metron/pull/949 > Migrate shuffle connections to local or shuffle > --- > > Key: METRON-1471 > URL: https://issues.apache.org/jira/browse/METRON-1471 > Project: Metron > Issue Type: Improvement >Reporter: Casey Stella >Priority: Major > > Currently, we use shuffle groupings when we do not want to group by field. > We should, instead, use local or shuffle groupings. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (METRON-1471) Migrate shuffle connections to local or shuffle
[ https://issues.apache.org/jira/browse/METRON-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391507#comment-16391507 ] ASF GitHub Bot commented on METRON-1471: GitHub user cestella reopened a pull request: https://github.com/apache/metron/pull/949 METRON-1471: Migrate shuffle connections to local or shuffle ## Contributor Comments Currently, we use shuffle groupings when we do not want to group by field. We should, instead, use local or shuffle groupings. Manual tests should include ensuring data continues to flow as before. ## Pull Request Checklist Thank you for submitting a contribution to Apache Metron. Please refer to our [Development Guidelines](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61332235) for the complete guide to follow for contributions. Please refer also to our [Build Verification Guidelines](https://cwiki.apache.org/confluence/display/METRON/Verifying+Builds?show-miniview) for complete smoke testing guides. In order to streamline the review of the contribution we ask you follow these guidelines and ask you to double check the following: ### 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- where 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 && dev-utilities/build-utils/verify_licenses.sh ``` - [x] Have you written or updated unit tests and or integration tests to verify your changes? - [x] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? - [x] Have you verified the basic functionality of the build by building and running locally with Vagrant full-dev environment or the equivalent? Note: Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible. It is also recommended that [travis-ci](https://travis-ci.org) is set up for your personal repository such that your branches are built there before submitting a pull request. You can merge this pull request into a Git repository by running: $ git pull https://github.com/cestella/incubator-metron local_or_shuffle_indexing Alternatively you can review and apply these changes as the patch at: https://github.com/apache/metron/pull/949.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 #949 commit 0ab26fa172a90eaf8eb441c8c085308649efdfb9 Author: cstella Date: 2018-03-06T16:18:57Z Updating the rest of the topologies to prefer local or shuffle over shuffle commit 82a7c823ab27441ddda5c043dee3cef8aa8f03be Author: cstella Date: 2018-03-08T14:25:19Z Merge branch 'master' into local_or_shuffle_indexing commit 2d3a7f68dc7570ca1a44b9b6a4b2880292e18824 Author: cstella Date: 2018-03-08T14:26:48Z Fixed profiler > Migrate shuffle connections to local or shuffle > --- > > Key: METRON-1471 > URL: https://issues.apache.org/jira/browse/METRON-1471 > Project: Metron > Issue Type: Improvement >Reporter: Casey Stella >Priority: Major > > Currently, we use shuffle groupings when we do not want to group by field. > We should, instead, use local or shuffle groupings. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (METRON-1483) Create a tool to monitor performance of the topologies
[ https://issues.apache.org/jira/browse/METRON-1483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391481#comment-16391481 ] ASF GitHub Bot commented on METRON-1483: GitHub user cestella opened a pull request: https://github.com/apache/metron/pull/958 METRON-1483: In performance evaluation, generating synthetic load and monitoring the write throughput of our kafka-to-kafka topologies has required a lot of custom scripting. We should have a tool that could do the following: Take a file representing a message template and generate synthetic load at a given events per second Monitor the kafka offsets of a topic and report throughput numbers in events per second ## Contributor Comments In performance evaluation, generating synthetic load and monitoring the write throughput of our kafka-to-kafka topologies has required a lot of custom scripting. We should have a tool that could do the following: * Take a file representing a message template and generate synthetic load at a given events per second * Monitor the kafka offsets of a topic and report throughput numbers in events per second Currently pending: * Test plan pending * Documentation ## Pull Request Checklist Thank you for submitting a contribution to Apache Metron. Please refer to our [Development Guidelines](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61332235) for the complete guide to follow for contributions. Please refer also to our [Build Verification Guidelines](https://cwiki.apache.org/confluence/display/METRON/Verifying+Builds?show-miniview) for complete smoke testing guides. In order to streamline the review of the contribution we ask you follow these guidelines and ask you to double check the following: ### 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- where 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? - [ ] 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 && dev-utilities/build-utils/verify_licenses.sh ``` - [x] Have you written or updated unit tests and or integration tests to verify your changes? - [x] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? - [x] Have you verified the basic functionality of the build by building and running locally with Vagrant full-dev environment or the equivalent? ### For documentation related changes: - [ ] Have you ensured that format looks appropriate for the output in which it is rendered by building and verifying the site-book? If not then run the following commands and the verify changes via `site-book/target/site/index.html`: ``` cd site-book mvn site ``` Note: Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible. It is also recommended that [travis-ci](https://travis-ci.org) is set up for your personal repository such that your branches are built there before submitting a pull request. You can merge this pull request into a Git repository by running: $ git pull https://github.com/cestella/incubator-metron perf_tool Alternatively you can review and apply these changes as the patch at: https://github.com/apache/metron/pull/958.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 #958 commit 8ba8c57576ed318d1ff3f69cda1dc9020d62352a Author: cstella Date: 2018-03-08T00:03:33Z Build load testing tool commit 638086f2f30cfe543b624721c1fb467062571eab Author: cstella Date: 2018-03-08T15:31:55Z refactoring monitoring to be more sensible. commit 55be01de033d0ea6b489930cb97fefcca80efdb5 Author: cstella Date: 2018-03-08T16:20:52Z Added summarization > Create a tool to monitor performance of the topologies > -- > >
[jira] [Created] (METRON-1483) Create a tool to monitor performance of the topologies
Casey Stella created METRON-1483: Summary: Create a tool to monitor performance of the topologies Key: METRON-1483 URL: https://issues.apache.org/jira/browse/METRON-1483 Project: Metron Issue Type: New Feature Reporter: Casey Stella In performance evaluation, generating synthetic load and monitoring the write throughput of our kafka-to-kafka topologies has required a lot of custom scripting. We should have a tool that could do the following: * Take a file representing a message template and generate synthetic load at a given events per second * Monitor the kafka offsets of a topic and report throughput numbers in events per second -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (METRON-1464) Convert schemas to be compatible with Solr 5.5.2
[ https://issues.apache.org/jira/browse/METRON-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391334#comment-16391334 ] ASF GitHub Bot commented on METRON-1464: Github user cestella commented on the issue: https://github.com/apache/metron/pull/945 Ok, I'm cool with it. +1 by inspection; great work. > Convert schemas to be compatible with Solr 5.5.2 > > > Key: METRON-1464 > URL: https://issues.apache.org/jira/browse/METRON-1464 > Project: Metron > Issue Type: Sub-task >Reporter: Ryan Merriman >Assignee: Ryan Merriman >Priority: Major > > It would be ideal if our Solr schemas were compatible with Solr 5.5.2 or > 6.6.2. This would be users the option of using a manually installed Solr or > HDP Search. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (METRON-1471) Migrate shuffle connections to local or shuffle
[ https://issues.apache.org/jira/browse/METRON-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391301#comment-16391301 ] ASF GitHub Bot commented on METRON-1471: Github user cestella commented on the issue: https://github.com/apache/metron/pull/949 @merrimanr Ah, I had forgotten to merge in master yesterday afternoon. There should be no more shuffles in any of the topologies. > Migrate shuffle connections to local or shuffle > --- > > Key: METRON-1471 > URL: https://issues.apache.org/jira/browse/METRON-1471 > Project: Metron > Issue Type: Improvement >Reporter: Casey Stella >Priority: Major > > Currently, we use shuffle groupings when we do not want to group by field. > We should, instead, use local or shuffle groupings. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (METRON-1482) Update REST to work with Solr
[ https://issues.apache.org/jira/browse/METRON-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391287#comment-16391287 ] ASF GitHub Bot commented on METRON-1482: Github user justinleet commented on the issue: https://github.com/apache/metron/pull/957 yeah, don't worry about it, it's not important, just a bit odd. > Update REST to work with Solr > - > > Key: METRON-1482 > URL: https://issues.apache.org/jira/browse/METRON-1482 > Project: Metron > Issue Type: Sub-task >Reporter: Ryan Merriman >Assignee: Ryan Merriman >Priority: Major > > Ambari should start REST with the correct Solr indexing jar on the classpath. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (METRON-1482) Update REST to work with Solr
[ https://issues.apache.org/jira/browse/METRON-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391280#comment-16391280 ] ASF GitHub Bot commented on METRON-1482: Github user merrimanr commented on the issue: https://github.com/apache/metron/pull/957 I've been maintaining this branch for a while and have been merging in other branches before they were committed to master. I think that's why you see all these commits. I merged in feature/METRON-1416-upgrade-solr right before I submitted this PR. It's the commit right before "fixed metron version". > Update REST to work with Solr > - > > Key: METRON-1482 > URL: https://issues.apache.org/jira/browse/METRON-1482 > Project: Metron > Issue Type: Sub-task >Reporter: Ryan Merriman >Assignee: Ryan Merriman >Priority: Major > > Ambari should start REST with the correct Solr indexing jar on the classpath. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (METRON-1355) Convert metron-elasticsearch to new infrastructure
[ https://issues.apache.org/jira/browse/METRON-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391273#comment-16391273 ] ASF GitHub Bot commented on METRON-1355: Github user justinleet commented on the issue: https://github.com/apache/metron/pull/941 No, that can wait for the follow-on ticket. Could you add a quick one-sentence blurb about the ElasticsearchTestUtils in the README so things are easier for anyone to test later (with the knowledge that it'll drop out in the later ticket)? > Convert metron-elasticsearch to new infrastructure > -- > > Key: METRON-1355 > URL: https://issues.apache.org/jira/browse/METRON-1355 > Project: Metron > Issue Type: Sub-task >Reporter: Ryan Merriman >Assignee: Ryan Merriman >Priority: Major > > Integration tests need to be converted to use the new infrastructure. This > includes: > # Updating clients with new infrastructure urls > # Adding a namespace to any assets the tests depend on > # Cleaning up interactions with old in memory infrastructure -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (METRON-1482) Update REST to work with Solr
[ https://issues.apache.org/jira/browse/METRON-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391270#comment-16391270 ] ASF GitHub Bot commented on METRON-1482: Github user justinleet commented on the issue: https://github.com/apache/metron/pull/957 There's a bunch of @cestella commits in here. Do you need to merge feature/METRON-1416-upgrade-solr into this PR? > Update REST to work with Solr > - > > Key: METRON-1482 > URL: https://issues.apache.org/jira/browse/METRON-1482 > Project: Metron > Issue Type: Sub-task >Reporter: Ryan Merriman >Assignee: Ryan Merriman >Priority: Major > > Ambari should start REST with the correct Solr indexing jar on the classpath. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
