[jira] [Commented] (NIFI-4361) Server fails to start during recovery upon full disk

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-4361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16157017#comment-16157017 ] 

ASF GitHub Bot commented on NIFI-4361:
--------------------------------------

GitHub user gresockj opened a pull request:

    https://github.com/apache/nifi/pull/2133

    NIFI-4361: Fixing early recovery shutdown due to EOF in walog partition

    Thank you for submitting a contribution to Apache NiFi.
    
    In order to streamline the review of the contribution we ask you
    to ensure the following steps have been taken:
    
    ### For all changes:
    - [x] Is there a JIRA ticket associated with this PR? Is it referenced 
         in the commit message?
    
    - [x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
    
    - [x] Has your PR been rebased against the latest commit within the target branch (typically master)?
    
    - [x] Is your initial contribution a single, squashed commit?
    
    ### For code changes:
    - [x] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
    - [ ] Have you written or updated unit tests to verify your changes?
    - [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? 
    - [ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
    - [ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
    - [ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?
    
    ### For documentation related changes:
    - [ ] Have you ensured that format looks appropriate for the output in which it is rendered?
    
    ### Note:
    Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gresockj/nifi NIFI-4361

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/nifi/pull/2133.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2133
    
----
commit 7457228bcfa7a2ec862f5395983fc4c5c3032faf
Author: Joe Gresock <jo...@lmco.com>
Date:   2017-09-07T14:32:43Z

    NIFI-4361: Fixing early recovery shutdown due to EOF in walog partition

----


> Server fails to start during recovery upon full disk
> ----------------------------------------------------
>
>                 Key: NIFI-4361
>                 URL: https://issues.apache.org/jira/browse/NIFI-4361
>             Project: Apache NiFi
>          Issue Type: Bug
>    Affects Versions: 1.1.0, 1.2.0, 1.3.0
>            Reporter: Joseph Gresock
>            Assignee: Joseph Gresock
>             Fix For: 1.4.0
>
>
> Our disk filled up -- we then freed up some space and restarted, but the server failed to start up due to:
> ERROR [main] o.a.nifi.controller.StandardFlowService Failed to load flow from cluster due to: org.apache.nifi.cluster.ConnectionException: Failed to connect node to cluster due to: java.lang.IllegalStateException: Signaled end to recovery, but there are more recovery files for Partition in directory /data/nifi/flowfile_repository/partition-8
> at org.wali.MinimalLockingWriteAheadLog$Partition.endRecovery(MinimalLockingWriteAheadLog.java:1047) ~[nifi-write-ahead-log-1.1.0.jar:1.1.0]
> at org.wali.MinimalLockingWriteAheadLog.recoverFromEdits(MinimalLockingWriteAheadLog.java:487) ~[nifi-write-ahead-log-1.1.0.jar:1.1.0]
> at org.wali.MinimalLockingWriteAheadLog.recoverRecords(MinimalLockingWriteAheadLog.java:301) ~[nifi-write-ahead-log-1.1.0.jar:1.1.0]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)