Support Questions

Find answers, ask questions, and share your expertise

Atlas application.log keeps increasing

avatar
Contributor

Hi All,

I added Atlas component on HDP2.5 , the Altlas status shown in Ambari is normal without any alerts as shown in bleow :

11458-screenshot-from-2017-01-17-17-07-19.png

However, when I watched Atlas log file application.log, in which the below INFO message are printed endlessly , and the size of application.log are also kept increasing.

2017-01-17 17:10:24,253 INFO  - [qtp699780352-19 - 3d52c102-c14b-42de-a41a-9cc8d60880d0:] ~ Audit: UNKNOWN/10.18.218.21 performed request GET http://hdp25node21:21000/api/atlas/admin/status (10.18.218.21) at time 2017-01-17T09:10Z (AuditFilter:91)
2017-01-17 17:10:24,253 INFO  - [qtp699780352-19 - 3d52c102-c14b-42de-a41a-9cc8d60880d0:] ~ Audit: UNKNOWN/10.18.218.21-10.18.218.21 performed request GET http://hdp25node21:21000/api/atlas/admin/status (10.18.218.21) at time 2017-01-17T09:10Z (AUDIT:104)
2017-01-17 17:10:25,617 INFO  - [qtp699780352-17 - 1a0b0647-cd66-41ba-9ff5-1d2e54536b14:] ~ Audit: UNKNOWN/10.18.218.21 performed request GET http://hdp25node21:21000/api/atlas/admin/status (10.18.218.21) at time 2017-01-17T09:10Z (AuditFilter:91)
2017-01-17 17:10:25,617 INFO  - [qtp699780352-17 - 1a0b0647-cd66-41ba-9ff5-1d2e54536b14:] ~ Audit: UNKNOWN/10.18.218.21-10.18.218.21 performed request GET http://hdp25node21:21000/api/atlas/admin/status (10.18.218.21) at time 2017-01-17T09:10Z (AUDIT:104)
2017-01-17 17:10:25,686 INFO  - [qtp699780352-18 - 7d0371fe-31fc-4e8d-b0e5-fa58df6e6318:] ~ Audit: UNKNOWN/10.18.218.21 performed request GET http://hdp25node21:21000/api/atlas/admin/status (10.18.218.21) at time 2017-01-17T09:10Z (AuditFilter:91)
2017-01-17 17:10:25,686 INFO  - [qtp699780352-18 - 7d0371fe-31fc-4e8d-b0e5-fa58df6e6318:] ~ Audit: UNKNOWN/10.18.218.21-10.18.218.21 performed request GET http://hdp25node21:21000/api/atlas/admin/status (10.18.218.21) at time 2017-01-17T09:10Z (AUDIT:104)
2017-01-17 17:10:28,861 INFO  - [qtp699780352-12 - 69a31ee6-6c3a-4e3a-8095-6b1a7685d7eb:] ~ Audit: UNKNOWN/10.18.218.21 performed request GET http://hdp25node21:21000/api/atlas/admin/status (10.18.218.21) at time 2017-01-17T09:10Z (AuditFilter:91)
2017-01-17 17:10:28,861 INFO  - [qtp699780352-12 - 69a31ee6-6c3a-4e3a-8095-6b1a7685d7eb:] ~ Audit: UNKNOWN/10.18.218.21-10.18.218.21 performed request GET http://hdp25node21:21000/api/atlas/admin/status (10.18.218.21) at time 2017-01-17T09:10Z (AUDIT:104)
2017-01-17 17:10:31,176 INFO  - [qtp699780352-19 - 3917084f-90dd-46d0-bd64-a1fd6a9b4633:] ~ Audit: UNKNOWN/10.18.218.21 performed request GET http://hdp25node21:21000/api/atlas/admin/status (10.18.218.21) at time 2017-01-17T09:10Z (AuditFilter:91)
2017-01-17 17:10:31,176 INFO  - [qtp699780352-19 - 3917084f-90dd-46d0-bd64-a1fd6a9b4633:] ~ Audit: UNKNOWN/10.18.218.21-10.18.218.21 performed request GET http://hdp25node21:21000/api/atlas/admin/status (10.18.218.21) at time 2017-01-17T09:10Z (AUDIT:104)

11460-screenshot-from-2017-01-17-17-13-33.png

Is this case above normal since I only saw "INFO" instead of "WARN" , "ERROR" in application.log file ?

Or is anything going wrong ? Because from my understanding , the log file are not supposed to be kept increasing so quickly la ?

application.log is attached as application.zip , any response or help is really appreciated !

application.zip


screenshot-from-2016-10-18-13-59-20.png
1 ACCEPTED SOLUTION

avatar
Expert Contributor

@Pengcheng Fang, If the log file only has INFO into it then you should enable log rotate mechanism for the atlas log file and it will not grow endlesly.

View solution in original post

3 REPLIES 3

avatar
Expert Contributor

@Pengcheng Fang, If the log file only has INFO into it then you should enable log rotate mechanism for the atlas log file and it will not grow endlesly.

avatar
Expert Contributor

Currently atlas is using DailyRollingFileAppender, so I think the log shouldn't endlessly grow, you should start seeing multiple files after a day or so.

avatar
Contributor

@hardik desai @anaik, thanks for your reply. Just like what anaik said, I can see multiple log files, such as application.log.2017-01-17 ... application.log.2017-01.xx within the atlas log folder, which means Atlas enables DailyRollingFileAppender log rotate mechanism by default.

Now that there is no ERROR and WARN appearing in application.log, that Audit: UNKNOWN/10.18.218.21 performed request GET so frequently is also a normal case for atlas, right ?

I just wonder why atlas needs to perform the GET request so frequently , and is there any place to config the frequence of sending GET request ?