geo: Check for transactions that must be global before taking transaction from pool #11731
Labels
area/docdb
YugabyteDB core features
kind/bug
This issue is a bug
priority/medium
Medium priority issue
Projects
Jira Link: [DB-341](https://yugabyte.atlassian.net/browse/DB-341)
Description
We currently take from local vs global transaction pools only based on the session variable. This results in transactions running into an error such as:
even when the first write is global. We should identify global transactions before taking a transaction from transaction pools when possible.
Context: #9980 #10158
The text was updated successfully, but these errors were encountered: