LARGE_DATA as XML

[Faaux]

Is there an exact XML Configuration somewhere that would be equivalent to the one used when setting builtinTransports to LARGE_DATA?

[cferreiragonz]

Hi @Faaux,

You can set LARGE_DATA directly from XML:

<?xml version="1.0" encoding="UTF-8" ?>
<dds xmlns="http://www.eprosima.com/XMLSchemas/fastRTPS_Profiles">
    <profiles>
        <participant profile_name="large_data_builtin_transports_options" is_default_profile="true">
            <rtps>
                <builtinTransports max_msg_size="4MB" sockets_size="4MB">LARGE_DATA</builtinTransports>
                <!-- Or without specifying options -->
                <builtinTransports>LARGE_DATA</builtinTransports>
            </rtps>
        </participant>
    </profiles>
</dds>

Also, you can configure something similar using the XML included in this section of the documentation, but it will not use Shared Memory for intra-host communication.

[Faaux]

Hi thanks for the quick answer.

Let me introduce some more context, as this is not what I am looking for.

I have multiple systems, VMs and Containers running that want to communicate with each other. While they can all see and talk to each other, FastDDS with LARGE_DATA doesnt seem to be able to establish connections.

What I want to do is to force certain network adapter to be used via the allowlist in the XML configuration file (which will be needed at some point in the future anyways, as during deployment of the project we will be part of a larger network where some network adapter are "off limits"). The issue is that I need both LARGE_DATA and the allowlist which are, as far as I can tell, mutually exclusive.

So while the example you posted is a great starting point it is not the complete configuration of LARGE_DATA, as you pointed out it is missing shared memory. Even adding just a shared memory transport_descriptor doesn't seem to produce the same results as LARGE_DATA.

I am currently on the road so this is just from memory. I configured the DomainQOS with LARGE_DATA or loaded it from a profile. LARGE_DATA had differences in both:

• transport
• wire_protocol

members. It at least had more unicast locators.

In short: I'd love to have the XML that reproduces LARGE_DATA as close as possible, so that I can adapt it with allowlist, blocklist and other settings

[cferreiragonz]

Hello @Faaux,

I am afraid that what you are looking for is currently not supported. It is not possible to replicate LARGE_DATA from XML files while using allowlist or blocklist.

I recommend reaching out to us at [email protected] with more details about your use case. Our team will be happy to evaluate your requirements and explore a custom solution that will work for you.

[Faaux]

Hi @cferreiragonz ,

E-Mail is sent, thanks for reaching out!