Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Deprecate Pubsub in Circulation domain

Description

Current situation or problem: mod-pubsub fails to deliver some of the events for unknown reasons. This issue cannot be reliably reproduced, but it happens every now and again on production which leads to automated patron blocks failures (MODPATBLK-183). The data can be re-syned manually as a workaround. It is thought that this issue comes from the fact that, by introducing another layer over Kafka, mod-pubsub is losing the delivery guarantees provided by Kafka. The issue can also be seen with fees/fines being applied to patrons too many times (MODFEE-388, MODPUBSUB-315).

Goal: Switch pubsub to kafka in circulation domain.

In scope
Review draft stories. Investigate, estimate, plan, and document the work required. Review and plan with solution architect. Consider impacts to
If there is capacity, consider beginning the work itself. If there is not, the feature will be split.

Out of scope

Use case(s)

Proposed solution/stories

Links to additional info

https://folio-org.atlassian.net/wiki/display/DD/PubSub+deprecation+plan 

Questions

Priority

Labels

Fix versions

Development Team

Vega

Assignee

Solution Architect

Parent

Parent Field Value

None

Parent Status

None

is cloned by

is continued by

is defined by

relates to

Checklist

hide

TestRail: Results

Activity

Show:

Charlotte Whitt June 8, 2023 at 10:41 AM

Thanks for responding so quickly . That was also our understanding, and great to get it confirmed.

Stephanie Buck June 7, 2023 at 7:48 PM
Edited

This resulted from a spike into what the effort would be if pubsub were deprecated. It is still in draft and is not scheduled because it is not a finalized feature, is not ready for development, and we do not know when or if this would occur. Please refer to the link in the feature description for more detailed information.

Charlotte Whitt June 7, 2023 at 11:23 AM

Hi - can you help us better understand the purpose of this work, when this work is planned to be executed, and the consequences on Circulation. I notice that the ticket is in Draft and is Not scheduled.

Maybe you also can refer me to a Wiki page with the architectural design for this change?

CC: and

Details

Reporter

PO Rank

0

Front End Estimate

Out of scope

Front End Estimator

Front-End Confidence factor

100%

Back End Estimate

XXXL: 30-45 days

Back End Estimator

Release

Not Scheduled

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created May 26, 2023 at 4:51 PM
Updated 5 days ago
Configure
TestRail: Cases
TestRail: Runs