[
https://issues.apache.org/jira/browse/METRON-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15687731#comment-15687731
]
ASF GitHub Bot commented on METRON-576:
---------------------------------------
Github user nickwallen commented on the issue:
https://github.com/apache/incubator-metron/pull/366
BTW, I also checked the Pcap Query tool to make sure there were no
unintended side effects, since that also uses Stellar to some degree. TL;DR;
I don't see any problems.
On Quick Dev, I started up Pcap Replay and Pycapa. I then started the pcap
topology to land data in HDFS. I ran a basic query that leveraged Stellar to
extract pcap. I received the expected data and it was correctly filtered. I
was also able to open it up in Wireshark.
```
service pcap-replay start
service pycapa start
bin/start_pcap_topology.sh
bin/pcap_query.sh query -q "ip_src_addr == '192.168.138.158'" -st 500
```
> Stellar function resolution takes too long on running cluster
> -------------------------------------------------------------
>
> Key: METRON-576
> URL: https://issues.apache.org/jira/browse/METRON-576
> Project: Metron
> Issue Type: Improvement
> Reporter: Nick Allen
> Assignee: Nick Allen
>
> When running the Stellar REPL in a cluster on AWS, function resolution takes
> 50-60 seconds. The user is not able to execute any functions in the REPL
> until this process completes.
> The default function resolver searches the classpath for Stellar functions.
> The delay may be because there are just too many classes in the classpath to
> search on a running cluster. As more libraries are added as dependencies
> under /usr/metron/<version>/lib this problem just gets worse.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
