pub_sub_model_sync 0.5.4 → 0.5.4.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 57e8d23c9e514734a8a45664f641378bbb46e8de5315c536a0f692efcbe29dd2
-  data.tar.gz: d0f290dac2b0563ffe5412f85e1a6a6e340e281049755b26dc732a3661501b92
+  metadata.gz: a06777a1f70a6efc94e7024b5b5c1f38d04f7eac8c9721a82fe84ffa042d15bb
+  data.tar.gz: f558c5116ec027c2b387dd04a16d03657d64f5fbefa244e9f075114cbd34ef21
 SHA512:
-  metadata.gz: 351901f98e6c806e7a4efe20abdac65de5bf8f716dc57e1889302eab02d33b3f2f4d449cd0d351fd5ae882d16abe79a77791bea8ad956c52cda47829319eb858
-  data.tar.gz: e906d601a8c37b999a8b6d550e605e9c04b67db692cec4b60220ae286bef9adde7132d8614cee4ca7dab9ef43538ae2baede3f07e402c4c21a189b79a9ba6873
+  metadata.gz: 41815c6d3390abcb71c3c4855e74e95ef7ead047e0e9315925eb8c1a56572f3458304d19bcdd38ceb51e203071f26a18071184fcbb766c47e5f617b2e0f530f4
+  data.tar.gz: 06f17b5f3ecfde95baf7c6465d371798a3257f2bbe86b288af4ab44250c8c8ff62faaa2597d4ddb520badf469a9558b2430e581d5d7c33bdfdd2d9e2ad83ae0a

data/CHANGELOG.md

@@ -1,5 +1,8 @@
 # Change Log
 
+# 0.5.4.1 (January 8, 2021)
+- fix: make sequential message processor google-pub/sub
+
 # 0.5.4 (January 8, 2021)
 - fix: exclude identifiers when syncing model
 - feat: callbacks support for future extra params

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    pub_sub_model_sync (0.5.4)
+    pub_sub_model_sync (0.5.4.1)
       rails
 
 GEM

data/README.md

@@ -312,6 +312,14 @@ config.debug = true
 - Auto publish update only if payload has changed
 - On delete, payload must only be composed by ids 
 
+## Q&A
+- Error "could not obtain a connection from the pool within 5.000 seconds"    
+  This problem occurs because pub/sub dependencies (kafka, google-pubsub, rabbitmq) use many threads to perform notifications where the qty of threads is greater than qty of DB pools ([Google pubsub info](https://github.com/googleapis/google-cloud-ruby/blob/master/google-cloud-pubsub/lib/google/cloud/pubsub/subscription.rb#L888))     
+  To fix the problem, edit config/database.yml and increase the quantity of ```pool: 10```
+- Google pubsub: How to process notifications parallely and not sequentially (default 1 thread)?    
+  ```ruby  PubSubModelSync::ServiceGoogle::LISTEN_SETTINGS = { threads: { callback: qty_threads } } ```    
+  Note: by this way some notifications can be processed before others thus missing relationship errors can appear 
+
 ## Contributing
 
 Bug reports and pull requests are welcome on GitHub at https://github.com/owen2345/pub_sub_model_sync. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct.

data/lib/pub_sub_model_sync/service_google.rb

@@ -7,6 +7,7 @@ end
 
 module PubSubModelSync
   class ServiceGoogle < ServiceBase
+    LISTEN_SETTINGS = { threads: { callback: 1 } }.freeze
     attr_accessor :service, :topic, :subscription, :subscriber
 
     def initialize

data/lib/pub_sub_model_sync/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module PubSubModelSync
-  VERSION = '0.5.4'
+  VERSION = '0.5.4.1'
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: pub_sub_model_sync
 version: !ruby/object:Gem::Version
-  version: 0.5.4
+  version: 0.5.4.1
 platform: ruby
 authors:
 - Owen