Alexey Serbin has posted comments on this change. ( http://gerrit.cloudera.org:8080/11409 )
Change subject: [docs] Add "one client only" best practice for kudu-spark ...................................................................... Patch Set 2: Code-Review+2 (1 comment) http://gerrit.cloudera.org:8080/#/c/11409/1/docs/developing.adoc File docs/developing.adoc: http://gerrit.cloudera.org:8080/#/c/11409/1/docs/developing.adoc@230 PS1, Line 230: To diagnose multiple `KuduClient` instances in a Spark job, look for signs in : the logs of the master being overloaded by many `GetTableLocations` or : `GetTabletLocations` requests coming from different clients, usually around the : same time > No, this issue is the problem with having multiple Kudu clients. Unfortunat I see. My questions was more about how to diagnose that condition at the master's side. Is that something about warnings about slow method execution in the paths of client metadata RPCs, etc.? How do you tell that the master is overloaded with client metadata RPCs? Any specific, but easy to see signs? -- To view, visit http://gerrit.cloudera.org:8080/11409 To unsubscribe, visit http://gerrit.cloudera.org:8080/settings Gerrit-Project: kudu Gerrit-Branch: master Gerrit-MessageType: comment Gerrit-Change-Id: Ibaf369315b8627674ba64e6418d153568ded6fe8 Gerrit-Change-Number: 11409 Gerrit-PatchSet: 2 Gerrit-Owner: Will Berkeley <wdberke...@gmail.com> Gerrit-Reviewer: Alexey Serbin <aser...@cloudera.com> Gerrit-Reviewer: Andrew Wong <aw...@cloudera.com> Gerrit-Reviewer: Dan Burkert <danburk...@apache.org> Gerrit-Reviewer: Will Berkeley <wdberke...@gmail.com> Gerrit-Comment-Date: Mon, 10 Sep 2018 18:29:40 +0000 Gerrit-HasComments: Yes
