It's doing 34,000 docs with 40 sim docs each on 8 cores so it is a bit slow anyway, still I shouldn't have to turn up the timeout so high should I?
I've been trying to get a rowsimilarity job to complete. It continues to
timeout on a RowSimilarityJob-CooccurrencesMapper-Reducer task so I've
upped the timeout to 30 minutes now. There are no errors in the logs
that I can see and no other task I've tried is acting like this. Is this
expected? Shouldn't the task check in more often?
- RowSimilarity error Pat Ferrel
- Re: RowSimilarity error Pat Ferrel
- Re: RowSimilarity error Sebastian Schelter
- Re: RowSimilarity error Pat Ferrel
- Re: RowSimilarity error Pat Ferrel
- Re: RowSimilarity error Sebastian Schelter
- Re: RowSimilarity error Pat Ferrel
- Re: RowSimilarity error Sebastian Schelter
- Re: RowSimilarity error Sebastian Schelter
- Re: RowSimilarity error Pat Ferrel
- Re: RowSimilarity error Pat Ferrel
