Grouper Users - Open Discussion List

["Hyzer, Chris" <>]

https://bugs.internet2.edu/jira/browse/GRP-1633

This is fixed in patch: 2.3.0 api #87

Defaults to have include/exclude happen in a transaction (can disable if you like), and defaults to not fix include/exclude by loader (afraid this might negatively affect people who edit include/exclude after creation and expects it not to be changed.  Plus, with transactions, should be good now.

include/exclude (loader or not) will run in transactions now, to use previous nontransactional behavior, set this to false in grouper.properties

# if should use transaction in include/exclude

grouperIncludeExcludeUseTransaction = true

to make the loader fix include/excludes, change this in grouper-loader.properties (by default it does not do this)

# fix include excludes on each run

loader.fixIncludeExcludes = false

Try it out and let me know how it goes.

Thanks

Chris

---

From: Scott Koranda <> on behalf of Scott Koranda <>
Sent: Friday, November 24, 2017 9:13 AM
To: Hyzer, Chris;
Subject: Fwd: [JIRA] (GRP-1633) make creation of include/exclude group structure by loader jobs transactional

 

Hi,

I think we talked about this issue informally, but there was not a JIRA
ticket to track it. So I created one.

Please let me know if the RFE is not clear or if I am incorrect and a
ticket already exists (I searched but could not find one).

Thanks,

Scott

P.S. Despite my JIRA account being tied to the email address
'', this is NOT a LIGO issue. I have another
client (a university) making this request.

This is the same deployment that is restarting the Grouper loader once
every day, and the restart causes the incomplete include/exclude group
structure now and then.

----- Forwarded message from "Scott Koranda (JIRA)" <> -----

Date: Fri, 24 Nov 2017 14:10:01 +0000 (UTC)
From: "Scott Koranda (JIRA)" <>
To:
Subject: [JIRA] (GRP-1633) make creation of include/exclude group structure by
        loader jobs transactional

Scott Koranda created GRP-1633:
----------------------------------

             Summary: make creation of include/exclude group structure by loader jobs transactional
                 Key: GRP-1633
                 URL: https://bugs.internet2.edu/jira/browse/GRP-1633
             Project: Grouper
          Issue Type: Improvement
      Security Level: Standard (Standard bug, may impact functionality but does not represent a security vulnerability)
          Components: grouperLoader
    Affects Versions: 2.3.0
            Reporter: Scott Koranda
            Assignee: Chris Hyzer
            Priority: Major


A grouper loader job may be configured to create the includes/excludes group structure. For example 

students_systemOfRecord
students includes
students excludes
students system of record and includes
students

The creation of the groups, however, is not transactional. If the loader process is killed or dies while the groups are being created the group structure can be incomplete with one or more of the groups missing. When the loader is restarted and that job run again the incomplete group structure is not detected and healed, but at the same time the creation of the group structure is skipped going forward, particularly if the creation of the SOR group did complete.

This is an RFE so that the creation of the group structure is transactional–the creation of the group structure should succeed completely or fail completely. Further, when the loader job next runs the creation of the group structure should be tried again if it did not succeed previously.



--
This message was sent by Atlassian JIRA
(v7.5.2#75007)

----- End forwarded message -----