Uploaded image for project: 'Log4j 2'
  1. Log4j 2
  2. LOG4J2-714

To Switch to Synchronous mode when there is an issue with PERSISTENT Database used in Flume Appender

    XMLWordPrintableJSON

    Details

    • Type: New Feature
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 2.1
    • Fix Version/s: None
    • Component/s: Flume Appender
    • Labels:
    • Environment:

      Red Hat Linux 5

      Description

      Hi Ralph,

      Hope your doing fine. Bhargava and I have come up with one more change along with the changes for the fix. Can you please let us know if this design is feasible and acceptable to the log4j flume appender community :

      To skip sending events when the environment (Berkley DB or NFS) is down. To create a new database environment once the environment is back. We will loose the events in this case when the environment is down. — I have made code changes for this issue. I am finding it hard to recreate the issue. I am currently working on the unit test cases.
      To switch to synchronous transfer of events when there is a problem with the database/NFS. This change is to prevent the loss of events. Once the environment is back, the code switches to Asynchronous mode. Please let us know your opinion on this.

      Regards,
      Avinash

        Attachments

        1. EnvironmentFailureException Patch.patch
          30 kB
          Avinash Dhananjay
        2. FlumeAppender.java
          21 kB
          Avinash Dhananjay
        3. FlumePersistentAppenderTest.java
          21 kB
          Avinash Dhananjay
        4. FlumePersistentManager.java
          39 kB
          Avinash Dhananjay
        5. pom.xml
          10 kB
          Avinash Dhananjay

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              adhanajay Avinash Dhananjay
            • Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:

                Time Tracking

                Estimated:
                Original Estimate - 336h
                336h
                Remaining:
                Remaining Estimate - 336h
                336h
                Logged:
                Time Spent - Not Specified
                Not Specified