Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a new feature to disable even log #1769

Closed
taojing2002 opened this issue Jan 9, 2024 · 1 comment
Closed

Add a new feature to disable even log #1769

taojing2002 opened this issue Jan 9, 2024 · 1 comment
Assignees
Milestone

Comments

@taojing2002
Copy link
Contributor

In this ticket, we have a steps to set up postgresql replication and rsync. After we get rid of Metacat replication, postgres replication, rsync and zookeeper will make the primary and secondary CN have the same content. In this case, the postgresql database in the secondary will be read-only. So, this cause two minor issue:

  • Any read activities can't be logged into database. We decided we can ignore those read activities on the secondary cn in one of our dev meetings. So this issue was resolved.
  • The Metacat instance on the secondary cn tries to log the read activities but gets an error the database can't be written (because of the postgresql replication settings).

Metacat still functions well but the second issue is annoying. So if we set a metacat property which can disable even log, the second issue will be gone.

@taojing2002 taojing2002 added this to the 3.0.0 milestone Jan 9, 2024
@taojing2002 taojing2002 self-assigned this Jan 9, 2024
@taojing2002
Copy link
Contributor Author

The feature branch was reviewed and merged into the develop branch.

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

No branches or pull requests

1 participant