You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your idea related to a problem? Please describe.
With the introduction of db names with just _shared in them ( like <db_name>_shared ) , it is likely that one particular db is supporting a lot of shares.
When a user is approving and revoking, lot of shares at a time, then this might lead to a lot of shares to keep on polling on the resource locks to acquire all the datasets where the db name is used ( #1706 ) . Due to this, the 10 mins timeout to acquire locks becomes less than required. Thus, in order to make all shares process , increase the timeout to maybe 30 mins or so, More importantly make the timeout configurable.
Good to have - If a share process is taking more than 20 mins to process, send an email to owners and requesters informing that the share processing is taking more than usual time to process
The text was updated successfully, but these errors were encountered:
Is your idea related to a problem? Please describe.
With the introduction of db names with just _shared in them ( like <db_name>_shared ) , it is likely that one particular db is supporting a lot of shares.
When a user is approving and revoking, lot of shares at a time, then this might lead to a lot of shares to keep on polling on the resource locks to acquire all the datasets where the db name is used ( #1706 ) . Due to this, the 10 mins timeout to acquire locks becomes less than required. Thus, in order to make all shares process , increase the timeout to maybe 30 mins or so, More importantly make the timeout configurable.
Good to have - If a share process is taking more than 20 mins to process, send an email to owners and requesters informing that the share processing is taking more than usual time to process
The text was updated successfully, but these errors were encountered: