Ruben Van Wanzeele created NIFI-14392:
-----------------------------------------

             Summary: Local state lost when migrating from 1.28 to 2.3
                 Key: NIFI-14392
                 URL: https://issues.apache.org/jira/browse/NIFI-14392
             Project: Apache NiFi
          Issue Type: Bug
            Reporter: Ruben Van Wanzeele


We experienced an issue with the state during migration

Our local state-management configuration looks as follows:
{code:java}
<local-provider>
  <id>local-provider</id>
  
<class>org.apache.nifi.controller.state.providers.local.WriteAheadLocalStateProvider</class>
  <property name="Directory">./state/local</property>
  <property name="Always Sync">false</property>
  <property name="Partitions">16</property>
  <property name="Checkpoint Interval">2 mins</property>
</local-provider> {code}
And before migration we have our state details correctly in the expected 
directory:
{code:java}
ls -la ./state/local/
total 92
drwxrwsr-x. 18 nifi nifi  4096 Mar 26 10:25 .
drwxrwsr-x.  8 root nifi  4096 Jan 17 02:14 ..
drwxrwsr-x.  2 nifi nifi  4096 Mar 26 10:25 partition-0
drwxrwsr-x.  2 nifi nifi  4096 Mar 26 10:25 partition-1
drwxrwsr-x.  2 nifi nifi  4096 Mar 26 10:25 partition-10
drwxrwsr-x.  2 nifi nifi  4096 Mar 26 10:25 partition-11
... 
drwxrwsr-x.  2 nifi nifi  4096 Mar 26 10:25 partition-8
drwxrwsr-x.  2 nifi nifi  4096 Mar 26 10:25 partition-9
-rw-r--r--.  1 nifi nifi 20448 Mar 26 10:25 snapshot
-rw-r--r--.  1 nifi nifi     0 Feb 19 21:28 wali.lock{code}
On a new environment with the same state-management configuration I see that 
the state information is stored in ./state/local/journals directory:
{code:java}
ls -la ./state/local/
total 16
drwxrwsr-x 3 nifi nifi 4096 Mar 26 10:23 .
drwxrwsr-x 9 root nifi 4096 Mar 24 12:27 ..
-rw-r--r-- 1 nifi nifi 2443 Mar 26 10:23 checkpoint
drwxrwsr-x 2 nifi nifi 4096 Mar 26 10:23 journals {code}
On a migrated environment I find both directory structures, and {*}the state 
from before 2.3 is not maintained{*}.

When searching the web, I found that this issue was already alerted, but not 
yet officially reported:

https://lists.apache.org/thread/5v59hbp18rpsboqc2q6f79h3b64803om



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to