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

ASF subversion and git services commented on ASTERIXDB-1701:
------------------------------------------------------------

Commit 8e043cfa1ea7a16463cc823a922deb92505fa55c in asterixdb's branch 
refs/heads/master from [~mhubail]
[ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=8e043cf ]

ASTERIXDB-1701: Fix log file boundry check

Change-Id: I538a8b931f3d50a00b092f218887a9731d14e235
Reviewed-on: https://asterix-gerrit.ics.uci.edu/1306
Sonar-Qube: Jenkins <jenk...@fulliautomatix.ics.uci.edu>
Tested-by: Jenkins <jenk...@fulliautomatix.ics.uci.edu>
Integration-Tests: Jenkins <jenk...@fulliautomatix.ics.uci.edu>
Reviewed-by: Ian Maxon <ima...@apache.org>
Reviewed-by: Michael Blow <mb...@apache.org>


> A txn log file partition may be used forever
> --------------------------------------------
>
>                 Key: ASTERIXDB-1701
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-1701
>             Project: Apache AsterixDB
>          Issue Type: Bug
>          Components: AsterixDB
>            Reporter: Murtadha Hubail
>            Assignee: Murtadha Hubail
>            Priority: Critical
>
> Currently, a log file partition size may be exceeded if the last log page 
> doesn't fall exactly at the boundary of the log file. Since we have variable 
> size log pages, a single log file may be used forever.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to