Details
-
Bug
-
Resolution: Fixed
-
None
-
High
-
Empty show more show less
Description
Problem
A TermTagger instance is not reachable in the time when it is tagging terms. So if the segments are bigger this leads to timeout messages when trying to connect to the termtagger.
solution
- Import: we decrease the segment bulk size from 50 to 5 fix in the PHP code and we remove the according config
- We increase the timeouts
- if we run into a timeout we do not mark the termtagger as DOWN (depending on how long the timeout was)
Attachments
Issue Links
- is duplicated by
-
TRANSLATE-1805 E1131 TermTagger DOWN, when termtaggers are only temporarily not reachable
- Done
-
TRANSLATE-824 TermTagger Connector must give an error when on the configured TCP port no termtagger is listening
- Done
Activity
Improve TermTagger usage when TermTagger is not reachable
Details
-
Bug
-
Resolution: Fixed
-
None
-
High
-
Empty show more show less
Description
Problem
A TermTagger instance is not reachable in the time when it is tagging terms. So if the segments are bigger this leads to timeout messages when trying to connect to the termtagger.
solution
- Import: we decrease the segment bulk size from 50 to 5 fix in the PHP code and we remove the according config
- We increase the timeouts
- if we run into a timeout we do not mark the termtagger as DOWN (depending on how long the timeout was)
Attachments
Issue Links
- is duplicated by
-
TRANSLATE-1805 E1131 TermTagger DOWN, when termtaggers are only temporarily not reachable
- Done
-
TRANSLATE-824 TermTagger Connector must give an error when on the configured TCP port no termtagger is listening
- Done