HornetQ I/O

Solution Verified - Updated -

Issue

  • Our system's I/O can't keep up with HornetQ. It indicates that a file could not opened during the HornetQ journal compacting phase. The most likely cause of this is that all the HornetQ nodes on a single blade store their journals on the same EXT4 filesystem, which implies that 6 HornetQ nodes are competing for the same I/O resources, which can cause issues under load.For performance reasons, Red Hat has advised us to put the HornetQ journals of the individual nodes on dedicated filesystems/disks.

  • Should it be a dedicated filesytem or a dedicated filesystem on a dedicated disk ?

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 6.0.1

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.