zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-3071) Add a config parameter to control transaction log size
Date Tue, 17 Jul 2018 00:47:00 GMT

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

Hadoop QA commented on ZOOKEEPER-3071:
--------------------------------------

-1 overall.  GitHub Pull Request  Build
      

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 2 new or modified tests.

    +1 javadoc.  The javadoc tool did not generate any warning messages.

    +1 javac.  The applied patch does not increase the total number of javac compiler warnings.

    -1 findbugs.  The patch appears to introduce 1 new Findbugs (version 3.0.1) warnings.

    +1 release audit.  The applied patch does not increase the total number of release audit
warnings.

    -1 core tests.  The patch failed core unit tests.

    +1 contrib tests.  The patch passed contrib unit tests.

Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1948//testReport/
Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1948//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/1948//console

This message is automatically generated.

> Add a config parameter to control transaction log size
> ------------------------------------------------------
>
>                 Key: ZOOKEEPER-3071
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3071
>             Project: ZooKeeper
>          Issue Type: Improvement
>          Components: server
>    Affects Versions: 3.6.0
>            Reporter: Suyog Mapara
>            Assignee: Suyog Mapara
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 3.6.0
>
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> Currently we only have a knob to control maximum number of transactions in the log file
but there is no direct way to control actual size of the file. This has implications on the
time it takes for a learner to sync using transaction log as the leader needs to seek the
file to find the appropriate transaction. This is a proposal for adding a config parameter
to control the transaction log size.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message