[
https://issues.apache.org/jira/browse/CONNECTORS-1432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16050986#comment-16050986
]
Karl Wright commented on CONNECTORS-1432:
-----------------------------------------
What deployment model are you using?
If you are using the multiprocess model with file system synchronization, it is
possible to wedge the system pretty well by killing processes using kill -9.
You should instead stop them using the scripts or commands provided, or better
yet use Zookeeper synchronization. If you do kill processes in that way, you
must following the standard lock-clean procedure, which involves:
- shutting them all down
- executing the lock-clean script
- starting them back up
FWIW, this has nothing whatsoever to do with the Tika transformer.
> Job with Tika will not save - no error popup
> --------------------------------------------
>
> Key: CONNECTORS-1432
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1432
> Project: ManifoldCF
> Issue Type: Bug
> Components: Tika extractor
> Affects Versions: ManifoldCF 2.7
> Environment: Ubuntu 16.10
> ElasticSearch
> File System
> Tika transform
> Reporter: Steph van Schalkwyk
> Assignee: Karl Wright
> Fix For: ManifoldCF 2.8
>
>
> When adding Tika to a job, it will only (and then only some times) add if
> this is the first configured job.
> All subsequent jobs added with Tika fail to save.
> Dropping the database solves it, but only for the first Job.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
