Skip to content

feat: introduce dedicated bucketing types - #8712

Open
chaen wants to merge 4 commits into
DIRACGrid:integrationfrom
chaen:v9.1_feat_dedicatedAccountingAgent
Open

feat: introduce dedicated bucketing types#8712
chaen wants to merge 4 commits into
DIRACGrid:integrationfrom
chaen:v9.1_feat_dedicatedAccountingAgent

Conversation

@chaen

@chaen chaen commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

This PR does 3 things:

  • optimize the AccountingDB with some caching
  • fixes a bug
  • Adds the possibility to split the DataStore bucketing based on the accounting type. It works, as we used it in LHCb, however it is probably not needed anymore after solving the 2 points above

BEGINRELEASENOTES

*Accounting
FIX: AccountingDB do not block for an hour after a bucketing error
FEAT: AccountingDB optimized with caching
FEAT: allow to split the DataStore based on AccountingType

ENDRELEASENOTES

@chaen
chaen force-pushed the v9.1_feat_dedicatedAccountingAgent branch 2 times, most recently from 0511f68 to 0f91cbb Compare July 23, 2026 12:03
@chaen
chaen force-pushed the v9.1_feat_dedicatedAccountingAgent branch 2 times, most recently from 970c555 to d51d3af Compare August 17, 2026 08:40
@chaen
chaen marked this pull request as ready for review August 17, 2026 08:40
Comment thread docs/source/AdministratorGuide/Systems/Accounting/index.rst
Comment thread docs/source/AdministratorGuide/Systems/Accounting/index.rst
Dedicated DataStore accounting
==============================

It is possible to run myltiple DataStore, each bucketing only certain type of accounting. It can be useful in case of backlog for certain types of accounting. It is however not recommended to run like that.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
It is possible to run myltiple DataStore, each bucketing only certain type of accounting. It can be useful in case of backlog for certain types of accounting. It is however not recommended to run like that.
It is possible to run multiple DataStore, each bucketing only certain type of accounting. It can be useful in case of backlog for certain types of accounting. It is however not recommended to run like that.

Why "it is not recommended"?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Because of the reason below: you need to keep a list of existing types

Comment thread src/DIRAC/AccountingSystem/ConfigTemplate.cfg Outdated
Comment thread src/DIRAC/AccountingSystem/DB/AccountingDB.py
@chaen
chaen force-pushed the v9.1_feat_dedicatedAccountingAgent branch from d51d3af to 4440a4d Compare September 2, 2026 09:27
@fstagni fstagni closed this Sep 4, 2026
@fstagni fstagni reopened this Sep 4, 2026
def initializeHandler(cls, svcInfoDict):
multiPath = PathFinder.getDatabaseSection("Accounting/MultiDB")
cls.__acDB = MultiAccountingDB(multiPath)
# we can focus on only some of the accoutning type

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
# we can focus on only some of the accoutning type
# we can focus on only some of the accounting type

{
Default = authenticated
}
# Specify which bucketing to run. Not recommended, see the docs

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
# Specify which bucketing to run. Not recommended, see the docs
# Specify for which of the existing Accounting types to run the bucketing. Not specifying this option means all of the accounting types, which is default and recommended. Refer to the official documentation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants