You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Michael Andre Pearce (JIRA)" <ji...@apache.org> on 2017/05/15 16:55:04 UTC
[jira] [Resolved] (ARTEMIS-1162) Make new Adapting TimedBuffer and
old Fixed TimedBuffer configurable
[ https://issues.apache.org/jira/browse/ARTEMIS-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Andre Pearce resolved ARTEMIS-1162.
-------------------------------------------
Resolution: Won't Fix
As per mailing list, and PR discussion it seems consensus will be the feature to be well tested, and version rollback being the supported solution to re-risk.
As such I'm closing this JIRA.
> Make new Adapting TimedBuffer and old Fixed TimedBuffer configurable
> --------------------------------------------------------------------
>
> Key: ARTEMIS-1162
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1162
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Affects Versions: 2.1.0
> Reporter: Michael Andre Pearce
> Fix For: 2.2.0
>
>
> New Adapting TimedBuffer was added and replaced existing Fixed TimedBuffer. This could cause behaviour/performance change of journal IO (and hopefully for the better).
> As this hasn't been run significantly in a real world production environment, to avoid causing any production deployment issues having unexpected behaviour changes, or to allow managed rollout and rollback.
> We would like to add back the fixed timed buffer (default), and make it configurable to the new improved timed buffer.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)