> On 13 Jun 2019, at 17:00, Mark Reynolds wrote:
>
>
> On 6/13/19 4:02 AM, William Brown wrote:
>>
>>> On 12 Jun 2019, at 17:36, Mark Reynolds wrote:
>>>
>>> http://www.port389.org/docs/389ds/design/repl-agmt-status-design.html
>>
>> Looks great!
>>
>> Instead of "Success" we could use
On 6/13/19 4:02 AM, William Brown wrote:
On 12 Jun 2019, at 17:36, Mark Reynolds wrote:
http://www.port389.org/docs/389ds/design/repl-agmt-status-design.html
Looks great!
Instead of "Success" we could use "Healthy" because replication isn't a success/fail, it's a longterm
"good/bad" IE
> On 12 Jun 2019, at 17:36, Mark Reynolds wrote:
>
> http://www.port389.org/docs/389ds/design/repl-agmt-status-design.html
Looks great!
Instead of "Success" we could use "Healthy" because replication isn't a
success/fail, it's a longterm "good/bad" IE healthy/failing state. So perhaps
On 6/12/19 12:53 PM, Rob Crittenden wrote:
Mark Reynolds wrote:
On 6/12/19 11:41 AM, Rob Crittenden wrote:
Mark Reynolds wrote:
http://www.port389.org/docs/389ds/design/repl-agmt-status-design.html
conn_error is 0 in all the examples. What would this be used for?
Well there are two type of
Mark Reynolds wrote:
>
> On 6/12/19 11:41 AM, Rob Crittenden wrote:
>> Mark Reynolds wrote:
>>> http://www.port389.org/docs/389ds/design/repl-agmt-status-design.html
>> conn_error is 0 in all the examples. What would this be used for?
> Well there are two type of errors that can occur. One is a
Sorry Mark, my email was confusing.
First you make a good point. Giving extra info does not hurt.
I just noticed that replication status contains two RC (ldap and
replication), while init status contains three RC (ldap, replication,
connection). So the json struct should differ from
On 6/12/19 12:08 PM, thierry bordaz wrote:
Hi Mark,
Looking very good to me.
For replication status there is either ldaprc or replrc. The message
is self explaining if it is a LDAP or replication error. IMHO I think
json could only contain 'repl_status' that can contain ldaprc or replrc.
Hi Mark,
Looking very good to me.
For replication status there is either ldaprc or replrc. The message is
self explaining if it is a LDAP or replication error. IMHO I think json
could only contain 'repl_status' that can contain ldaprc or replrc.
For init status, it exists ldaprc, connrc and
On 6/12/19 11:41 AM, Rob Crittenden wrote:
Mark Reynolds wrote:
http://www.port389.org/docs/389ds/design/repl-agmt-status-design.html
conn_error is 0 in all the examples. What would this be used for?
Well there are two type of errors that can occur. One is a replication
error (missing CSN,
Mark Reynolds wrote:
> http://www.port389.org/docs/389ds/design/repl-agmt-status-design.html
conn_error is 0 in all the examples. What would this be used for?
Otherwise this looks ok to me. I assume we'll need to do coordinate
releases with IPA so the new format can be handled properly? I guess
10 matches
Mail list logo
