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

move from error to warn #142

Merged
merged 5 commits into from
Feb 9, 2024
Merged

move from error to warn #142

merged 5 commits into from
Feb 9, 2024

Conversation

kishansairam9
Copy link
Contributor

No description provided.

@@ -508,7 +508,7 @@ server:
type: pd-standard

logging:
level: error
level: warn
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it already is set to error in helm-values repo.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We will adjust in helm-values repo as needed

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what I meant was that we already have set the logging level to error. are there any specific warn logs we are interested in? there were too much logging by pinot.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Laxman and mihir were of opinion we should have warn logs and fix any underlying issues

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I only suggested better to keep warn as the default.
If they are too noisy, we may need to investigate and fix or turn them off at package level in worst case.

@@ -11,7 +11,7 @@ metadata:
heritage: {{ .Release.Service }}
data:
pinot-controller-log4j2.xml: |-
<Configuration>
<Configuration monitorInterval="30">
Copy link
Contributor Author

@kishansairam9 kishansairam9 Feb 8, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same with this, we will be modifying in helm-values if overriden

@@ -25,7 +25,7 @@ data:
<AppenderRef ref="console"/>
</Root>
<AsyncLogger name="org.reflections" level="error" additivity="false"/>
<AsyncLogger name="org.apache.pinot.broker.querylog.QueryLogger" level="info"/>
<Logger name="org.apache.pinot.broker.querylog.QueryLogger" level="info" additivity="false"/>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Logger need to have console appenderRef.

@laxmanchekka laxmanchekka merged commit a7ba715 into main Feb 9, 2024
6 checks passed
@laxmanchekka laxmanchekka deleted the log-tune branch February 9, 2024 18:08
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

Successfully merging this pull request may close these issues.

3 participants