[ 
https://issues.apache.org/jira/browse/ARTEMIS-2483?focusedWorklogId=310074&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-310074
 ]

ASF GitHub Bot logged work on ARTEMIS-2483:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 10/Sep/19 20:16
            Start Date: 10/Sep/19 20:16
    Worklog Time Spent: 10m 
      Work Description: clebertsuconic commented on pull request #2833: 
ARTEMIS-2483 Sync calculation should use the block size
URL: https://github.com/apache/activemq-artemis/pull/2833
 
 
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 310074)
    Remaining Estimate: 0h
            Time Spent: 10m

> BlockSize is not used on sync calculation on CLI create
> -------------------------------------------------------
>
>                 Key: ARTEMIS-2483
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2483
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 2.10.0
>            Reporter: clebert suconic
>            Assignee: clebert suconic
>            Priority: Major
>             Fix For: 2.11.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> During an ./artemis create, the block size is not passed to libaio, letting 
> it use the default value from the device.
> This is particularly dangerous as some MDS providers will return a huge block 
> size (e.g. ceph-fs).
> instead we should always use 4K if calculation sync times on libaio.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Reply via email to