[jira] [Resolved] (CONNECTORS-1619) When you edit the Elastic Output connector, you need to set the password again

[ https://issues.apache.org/jira/browse/CONNECTORS-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Markus Schuch resolved CONNECTORS-1619. --- Resolution: Fixed > When you edit the Elastic Output connector, you need to set

[jira] [Commented] (CONNECTORS-1619) When you edit the Elastic Output connector, you need to set the password again

[ https://issues.apache.org/jira/browse/CONNECTORS-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16909395#comment-16909395 ] Markus Schuch commented on CONNECTORS-1619: --- r1865329 (trunk) > When you edit the

[jira] [Updated] (CONNECTORS-1619) When you edit the Elastic Output connector, you need to set the password again

[ https://issues.apache.org/jira/browse/CONNECTORS-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Markus Schuch updated CONNECTORS-1619: -- Fix Version/s: ManifoldCF 2.14 > When you edit the Elastic Output connector, you

[jira] [Commented] (CONNECTORS-1619) When you edit the Elastic Output connector, you need to set the password again

[ https://issues.apache.org/jira/browse/CONNECTORS-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16909393#comment-16909393 ] Markus Schuch commented on CONNECTORS-1619: --- The password is mapped to a "key" when

[jira] [Commented] (CONNECTORS-1619) When you edit the Elastic Output connector, you need to set the password again

[ https://issues.apache.org/jira/browse/CONNECTORS-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16909380#comment-16909380 ] Markus Schuch commented on CONNECTORS-1619: --- Thanks for your bug report. It is

[jira] [Assigned] (CONNECTORS-1619) When you edit the Elastic Output connector, you need to set the password again

[ https://issues.apache.org/jira/browse/CONNECTORS-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Markus Schuch reassigned CONNECTORS-1619: - Assignee: Markus Schuch > When you edit the Elastic Output connector, you

[jira] [Created] (CONNECTORS-1619) When you edit the Elastic Output connector, you need to set the password again

Michael Cizmar created CONNECTORS-1619: -- Summary: When you edit the Elastic Output connector, you need to set the password again Key: CONNECTORS-1619 URL:

Re: ManifoldCF Resource Offering

Yes, absolutely. We'll program to the core interfaces, get them documented, and unit tested. Typically our first step is to mock the service that we are programming against and the approach the development in a TDD fashion. In our world, we don't have extensive debugging capabilities so we have

Re: ManifoldCF Resource Offering

If you could structure this as one contribution at a time I would be grateful. That way, problems with one contribution won't block others. We also like to have an integration test for each connector. Not all of them have this at this time, but it's very very helpful if you have the time to put

Re: Unexpected HTTP result code: -1: null

Sure I will try to do that.. and will get back to you Sent from my iPhone > On 16-Aug-2019, at 6:23 PM, Michael Cizmar wrote: > > Priya - Was this right? > > 48GB and 1-Core Intel(R) Xeon(R) CPU > > While not directly related to an out of memory issue, you should have more > cores allocated

Re: Unexpected HTTP result code: -1: null

Priya - Was this right? 48GB and 1-Core Intel(R) Xeon(R) CPU While not directly related to an out of memory issue, you should have more cores allocated to ES. On Fri, Aug 16, 2019 at 1:09 AM Priya Arora wrote: > *Existing Threads/connections configuration is :-* > > How many worker threads

Re: ManifoldCF Resource Offering

For better or worse, my company (MC+A ) was know for a period of time as a 'connector' company although we are a consultancy. What I'm thinking initially: 1. Connector development for repositories like (effectively looking at what we have and migrating them to

Re: Unexpected HTTP result code: -1: null

Hi Priya, Set Xms and Xmx values as same. Try with a fairly bigger value, i.e. 4096m or more and share the result. Then we can adjust that value. What is your main purpose to use ManifoldCF, just web crawl? If so, you can check Apache Nutch project too. Kind Regards, Furkan KAMACI 16 Ağu 2019

Re: Unexpected HTTP result code: -1: null

Hi Furkan, These are the configuration defined I have -Xms1024m ,-Xmx1024m memory allocated *in start-options.env.unix, start-options.env.win* file. Also Configuration:- 1) For Crawler server - 16 GB RAM and 8-Core Intel(R) Xeon(R) CPU E5-2660 v3 @ 2.60GHz and -ManifolCF 2) For Elasticsearch

Re: Unexpected HTTP result code: -1: null

Hi Priya, What is your GC params and does it throw error at a particular Zip file? Check its size and if much, consider limiting allowed file size to ingest. Kind Regards, Furkan KAMACI 16 Ağu 2019 Cum, saat 13:40 tarihinde Karl Wright şunu yazdı: > I see nothing indicating any single Tika

Re: Unexpected HTTP result code: -1: null

I see nothing indicating any single Tika extraction content type. It's basically just unhappy with heap fragmentation and is GC'ing too frequently. I would suggest just increasing the amount of memory you give the process for an experiment. This might allow it to succeed. MCF uses the

Re: Unexpected HTTP result code: -1: null

Please Find below error stack trace:- ERROR: agents process ran out of memory - shutting down java.lang.OutOfMemoryError: GC overhead limit exceeded at java.util.HashMap.newNode(HashMap.java:1750) at java.util.HashMap.putVal(HashMap.java:631) at

Re: Unexpected HTTP result code: -1: null

Without an out-of-memory stack trace, I cannot definitively point to Tika or say that it's a specific kind of file. Please send one. Karl On Fri, Aug 16, 2019 at 2:09 AM Priya Arora wrote: > *Existing Threads/connections configuration is :-* > > How many worker threads do you have? - 15

[jira] [Comment Edited] (CONNECTORS-1618) Maven javadoc build fails due to linter errors

[ https://issues.apache.org/jira/browse/CONNECTORS-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16908830#comment-16908830 ] Markus Schuch edited comment on CONNECTORS-1618 at 8/16/19 7:58 AM:

[jira] [Comment Edited] (CONNECTORS-1618) Maven javadoc build fails due to linter errors

[ https://issues.apache.org/jira/browse/CONNECTORS-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16908830#comment-16908830 ] Markus Schuch edited comment on CONNECTORS-1618 at 8/16/19 7:57 AM:

[jira] [Commented] (CONNECTORS-1618) Maven javadoc build fails due to linter errors

[ https://issues.apache.org/jira/browse/CONNECTORS-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16908830#comment-16908830 ] Markus Schuch commented on CONNECTORS-1618: --- Travis Maven Build and Maven Javadoc Build

Re: ManifoldCF Resource Offering

Hi Michael, Thanks for your interest! Community is important for FOSS projects. It can both help to develop such improvements and use it as may need them. So, in my opinion you can share which parts do you want to improve/add and share it with us for both some can help you and need them. Kind

[jira] [Commented] (CONNECTORS-1618) Maven javadoc build fails due to linter errors

[ https://issues.apache.org/jira/browse/CONNECTORS-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16908768#comment-16908768 ] Markus Schuch commented on CONNECTORS-1618: --- r1865267 (branches/CONNECTORS-1618) - fixes

Re: Unexpected HTTP result code: -1: null

*Existing Threads/connections configuration is :-* How many worker threads do you have? - 15 worker threads has been allocated(in properties.xml file). And the Tika Extractor connections -10 connections are defined. Is this suggested to reduce the number more. If not, what else can be a solution