Story #8771
Updated by Roger Dahl over 5 years ago
When a submitting a Node doc update which includes a nodeReplicationPolicy, this section is good:
```
<nodeReplicationPolicy>
<maxObjectSize>21474836480</maxObjectSize>
<spaceAllocated>1099511627776</spaceAllocated>
</nodeReplicationPolicy>
```
while the same section without `maxObjectSize` returns error:
```
<error detailCode="4822" errorCode="500" name="ServiceFailure">
<description>updateNodeCapabilities failed due to LDAP communication failure:: InvalidAttributeValueException:[LDAP: error code 21 - d1ReplicationPolicyMaxObjectSize: value #0 invalid per syntax]:[LDAP: error code 21 - d1ReplicationPolicyMaxObjectSize: value #0 invalid per syntax]</description>
</error>
```
The schema allows leaving `maxObjectSize` out, which means that the MN accepts replicas of unlimited size.
Both GMN and Metacat leave `maxObjectSize` out if the setting is configured to unlimited with `-1`.
I think it used to work.
```
<nodeReplicationPolicy>
<maxObjectSize>21474836480</maxObjectSize>
<spaceAllocated>1099511627776</spaceAllocated>
</nodeReplicationPolicy>
```
while the same section without `maxObjectSize` returns error:
```
<error detailCode="4822" errorCode="500" name="ServiceFailure">
<description>updateNodeCapabilities failed due to LDAP communication failure:: InvalidAttributeValueException:[LDAP: error code 21 - d1ReplicationPolicyMaxObjectSize: value #0 invalid per syntax]:[LDAP: error code 21 - d1ReplicationPolicyMaxObjectSize: value #0 invalid per syntax]</description>
</error>
```
The schema allows leaving `maxObjectSize` out, which means that the MN accepts replicas of unlimited size.
Both GMN and Metacat leave `maxObjectSize` out if the setting is configured to unlimited with `-1`.
I think it used to work.