Uploaded image for project: 'Blazegraph (by SYSTAP)'
  1. Blazegraph (by SYSTAP)
  2. BLZG-197 BlazeGraph release 2.1 (Scale-out GA)
  3. BLZG-2

Change the default cluster logging setup to use service local logging rather than log aggregation.

    XMLWordPrintable

    Details

    • Type: Sub-task
    • Status: In Progress
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Bigdata Federation
    • Labels:
      None

      Description

      Change the default logging setup to use per-service logging. The cluster install currently sets up a log4j org.apache.log4j.net.SimpleSocketServer which aggregates all log messages to a single host. This is controlled by the bigdataup script, build.properties (which host runs the log4j server), and src/config/resources/log4j{Server}.properties. This is convenient for testing, but not scalable.

      When log aggregation is required, SeanG has worked out how to setup syslog for log aggregation on a cluster. This would make it possible for us to capture logs from non-log4j components. That insight should be captured in the configuration files and documented on the wiki.

        Attachments

          Activity

            People

            Assignee:
            beebs Brad Bebee
            Reporter:
            bryanthompson bryanthompson
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated: