[NIFI-7544] ReplaceText processor seems not thread-safe?

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 1.11.4
• Fix Version/s: 1.12.0
• Component/s: Core Framework
• Environment: Red Hat Enterprise Linux 7.8 ; openjdk version "11.0.7" 2020-04-14 LTS ; OpenJDK Runtime Environment 18.9 (build 11.0.7+10-LTS) ; OpenJDK 64-Bit Server VM 18.9 (build 11.0.7+10-LTS, mixed mode, sharing)
• Assignee: Unassigned
• Reporter: Milco Numan
• Created: 17/Jun/20 04:59
• Updated: 31/Aug/20 13:22
• Resolved: 31/Aug/20 13:22

Description

We have a flow where there are separate flow files containing a single string. We use the ReplaceText processor to prepend this string by a parameter name (for use in an actual URI, as query parameter) and postfix the string by an ampersand: 

When using this processor with number of concurrrent tasks > 1 (4 in our case), we have seen it happening that content of file-A is inserted as the result of file-B, it seems as if the process is not thread safe where the actual search value is captured.

We can see from the logfile (created by inserting LogAttribute processors logging uuid and the actual content after all steps in the process) that the input of one file is overwritten with the search/replace pattern of another file (just before it), see uploaded log file

 

Issue Links

• duplicates: NIFI-7683 ReplaceText with multiple concurrency tasks can result in data corruption