GitHub user ouyangshourui opened a pull request:

    https://github.com/apache/spark/pull/10549

    size RollingPolicy shouldRollover loginfo should change to logDebug

    https://issues.apache.org/jira/browse/SPARK-12601
    when using size RollingPolicythis code cause worker output a large of log 
.it shoud be changed to logDebug
    the code as following:
     /** Should rollover if the next set of bytes is going to exceed the size 
limit */
      def shouldRollover(bytesToBeWritten: Long): Boolean = {
        logDebug(s"$bytesToBeWritten + $bytesWrittenSinceRollover > 
$rolloverSizeBytes")
        bytesToBeWritten + bytesWrittenSinceRollover > rolloverSizeBytes
      }
    
    -->
    
     /** Should rollover if the next set of bytes is going to exceed the size 
limit */
      def shouldRollover(bytesToBeWritten: Long): Boolean = {
        logDebug(s"$bytesToBeWritten + $bytesWrittenSinceRollover > 
$rolloverSizeBytes")
        bytesToBeWritten + bytesWrittenSinceRollover > rolloverSizeBytes
      }


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

    $ git pull https://github.com/ouyangshourui/spark rollingsizeloginfo

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

    https://github.com/apache/spark/pull/10549.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 #10549
    
----
commit ec1fc25f12dfd77146be3ad3931fbdcc1ff680eb
Author: ouyangshourui <[email protected]>
Date:   2016-01-02T03:41:17Z

    size RollingPolicy shouldRollover loginfo should change to logDebug

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to