#general
@randxiexyy29: @randxiexyy29 has joined the channel
@stavg: @stavg has joined the channel
@rohitdev.kulshrestha: @rohitdev.kulshrestha has joined the channel
#random
@randxiexyy29: @randxiexyy29 has joined the channel
@stavg: @stavg has joined the channel
@rohitdev.kulshrestha: @rohitdev.kulshrestha has joined the channel
#troubleshooting
@nadeemsadim: Hi folks .. most probably because of having inverted indexing on high cardinality data .. some memory leak is happening on pinot server pods .. and ram usage gradually increases by few hundred mb every day .. temporary resolution to free heap/ram memory we are thinking of is trying to restart pinot server pods on weekly basis using command:- *kubectl delete po dev-pinot-server-0 dev-pinot-server-1 dev-pinot-server-2 -n dev-pinot* *will it cause any data loss or table and schema and data in table will remain intact after restart/bouncing of pinot server pods..* *ref:*
@mayanks: Can you create a Github issue with as much details as possible for helping debug and fix the memory issue you are reporting, that would be great. Note, that Pinot is running in huge deployments in production and this issue hasn't been reported, so it might be specific to your usecase or setup. So if you can provide all the details, we can help debug/fix the issue.
@nadeemsadim: @mayanks we need to take heap dump/thread dump in case we need to create a github issue ? also can somebody confirm if we perform *kubectl delete po dev-pinot-server-0 dev-pinot-server-1 dev-pinot-server-2 -n dev-pinot* *will it cause any data loss or table and schema and data in table will remain intact after restart/bouncing of pinot server pods..*
@nadeemsadim: Also we are using on useG1Gc in garbage collection .. no printGC etc right now
@mayanks: Yes, that would be good, you can also provide info like: ```1. Graphs 2. Release you are using 3. Use case related info (read/write qps) 4. Is leak in offline or realtime, if RT, the server configs, etc```
@nadeemsadim: we are using realtime
@nadeemsadim: already xiang confirmed once before than table and data will remain intact .. heap dump I will take and respond here and proceed for github issue once verified
@xiangfu0: How do you get ram usage?
@xiangfu0: If it's from k8s container memory usage, then it's expected
@xiangfu0: You should check jvm usage
@xiangfu0: Also kubectl delete won't cause data loss
@nadeemsadim: By using kubectl top po -n dev-pinot
@nadeemsadim: Got the ram usage
@xiangfu0: it’s k8s container pod memory usage. You should track jvm memory usage and gc happening.
@randxiexyy29: @randxiexyy29 has joined the channel
@stavg: @stavg has joined the channel
@rohitdev.kulshrestha: @rohitdev.kulshrestha has joined the channel
@sandeep.hadoopadmn: Hi Guys, I stood up pinot cluster with in one node, and created schema and integrated kafka broker to it. I tried inserting some sample data, but it is falling to consumer from pinot, getting below error, ```), currentOffset=1939499, numRowsConsumedSoFar=1, numRowsIndexedSoFar=1 2021/10/31 23:08:26.026 ERROR [LLRealtimeSegmentDataManager_pnrevents__0__0__20211031T2306Z] [pnrevents__0__0__20211031T2306Z] Caught exception while transforming the record: { "fieldToValueMap" : { "pt" : null, "osia" : null, "excludePII" : 0, "pcc" : null, "lname" : null, "mel" : null, "tkt" : null, "kafkaProps" : null, "timestamp" : null, "ver" : null, "dts" : null, "proxyUrl" : "
#pinot-dev
@falexvr: @falexvr has joined the channel
@falexvr: Good morning guys, I'm in the middle of writing a scala client using your java client as the base but I'm confused with something I just saw and don't know why is coded like that
@falexvr: For your reference, I'm talking about this one:
@falexvr: And what I don't understand is this method:
@falexvr: Why do you do this if the second line overrides what the first line does?
@falexvr:
@falexvr:
@falexvr: I'd get it if that was some sort of appending operation but it is not
@xiangfu0: I think it’s a bug that textTable doesn’t hold the column data types. We should fix that
@xiangfu0: Thanks for pointing this out @falexvr
@g.kishore: can you please file an issue
#announcements
@rohitdev.kulshrestha: @rohitdev.kulshrestha has joined the channel
#getting-started
@alexj.nich: @alexj.nich has joined the channel
@rohitdev.kulshrestha: @rohitdev.kulshrestha has joined the channel
--------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@pinot.apache.org For additional commands, e-mail: dev-h...@pinot.apache.org
