https://pinot.apache.org/ logo
#troubleshooting
Title
# troubleshooting
w

Weixiang Sun

03/11/2022, 8:43 PM
Does any see the following exception with the query against upsert table? I do not see the problem with offline table.
Copy code
Caused by: java.lang.IllegalArgumentException: The datetime zone id 'America/Los_Angeles' is not recognised
        at org.joda.time.DateTimeZone.forID(DateTimeZone.java:247) ~[pinot-all-0.8.0-jar-with-dependencies.jar:0.8.0-d53965c35d75bff2fbe92706129cac9ca563aac3]
        at org.apache.pinot.common.function.scalar.DateTimeFunctions.year(DateTimeFunctions.java:335) ~[pinot-all-0.8.0-jar-with-dependencies.jar:0.8.0-d53965c35d75bff2fbe92706129cac9ca563aac3]
        at jdk.internal.reflect.GeneratedMethodAccessor1636.invoke(Unknown Source) ~[?:?]
        at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
        at java.lang.reflect.Method.invoke(Method.java:566) ~[?:?]
        at org.apache.pinot.common.function.FunctionInvoker.invoke(FunctionInvoker.java:128) ~[pinot-all-0.8.0-jar-with-dependencies.jar:0.8.0-d53965c35d75bff2fbe92706129cac9ca563aac3]
        ... 19 more
x

Xiaobing

03/11/2022, 9:53 PM
could you share an example query?
feels like this may be easy to reproduce on my side.
w

Weixiang Sun

03/11/2022, 11:21 PM
Thanks a lot for your help! @Xiaobing The problem is that the pinot server is in bad state
👌 1
e

Elon

03/15/2022, 10:25 PM
Restarting the servers seem to help, could this be an issue with joda library having an issue initializing? Anyone else see this error?
The errors show up in the server error logs
x

Xiaobing

03/15/2022, 10:52 PM
thanks for sharing the issue. any clues to help reproduce this issue?
e

Elon

03/15/2022, 10:53 PM
At this point just those log messages in the server and the fact that restarting clears those errors. We will continue to monitor and if we have any more info we'll share it
👍 1
Have you seen this before?
x

Xiaobing

03/15/2022, 10:53 PM
I haven’t seen
👍 1
e

Elon

03/15/2022, 10:54 PM
Strange too - most of the stack overflow or other searches report that it's due to an older version of joda, but Pinot uses a recent version...
x

Xiaobing

03/15/2022, 10:58 PM
yeah, I just spotted
pinot-all-0.8.0
in the log msg above. but found that 0.8.0 release used the same joda lib as seen on the current master branch of Pinot.
Copy code
<dependency>
        <groupId>joda-time</groupId>
        <artifactId>joda-time</artifactId>
        <version>2.10.5</version>
      </dependency>
💡 2
w

Weixiang Sun

03/15/2022, 11:09 PM
@Xiaobing did you see any weird issue resolved by restarting pinot server?
x

Xiaobing

03/15/2022, 11:23 PM
hmm.. not really to my own experience.