Uninstalled requests and urllib3, and installed requests 2.6.1, and am
still seeing a similar issue on launch.
On Tue, Feb 27, 2018 at 2:19 PM, Ryan Merriman wrote:
> Here is what I see in our Ansible scripts:
>
> - name: Install python-requests module
> pip:
> name:
Here is what I see in our Ansible scripts:
- name: Install python-requests module
pip:
name: requests
version: 2.6.1
I would try installing that exact version with pip. Also, have you tried
installing that dependency?
On Tue, Feb 27, 2018 at 1:14 PM, David McGinnis
Is there a fix available already, or how would you go about making this
fix? I'm open to figuring it out if you have any ideas on how we should fix
the issue. Requests was installed for me already without pip even being
installed, likely through the MPack process or as part of a previously
Yep you found it. You were unlucky enough to install a version of master
that had this regression. How did you install requests? Using pip should
also install the necessary dependencies. Either way everything should
still work, you'll just have to manually start/stop indexing since you
won't
Looks like this issue was introduced in this commit:
https://github.com/apache/metron/commit/1c9437c41c4eb626bd44
193ec6545f9356f3f7b2 . Looking past this, there is only one commit that
seems to deal with this, but it is for the Ansible deployment, so I don't
believe it would affect an MPack
*Simon:*
There are some errors from processing showing up in the indexing topic, but
no data is making it through without restarting Metron completely
(restarting just the indexing service doesn't seem to do it).
I don't have easy access to the Storm UI at the moment. I have a work
around to get