[jira] [Updated] (RANGER-2021) Ranger "Login Sessions" Audits impossible to browse due to 'rangerusersync'
[
https://issues.apache.org/jira/browse/RANGER-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Velmurugan Periasamy updated RANGER-2021:
-
Fix Version/s: 1.1.0
> Ranger "Login Sessions" Audits impossible to browse due to 'rangerusersync'
> ---
>
> Key: RANGER-2021
> URL: https://issues.apache.org/jira/browse/RANGER-2021
> Project: Ranger
> Issue Type: Bug
> Components: usersync
>Affects Versions: 0.7.0
>Reporter: Sean Roberts
>Assignee: Nikhil Purbhe
>Priority: Major
> Fix For: 1.1.0
>
> Attachments:
> RANGER-2021-RANGER-2064-Ranger-Usersync-should-use-c.patch,
> RANGER-2021-Ranger-Login-Sessions-Audits-impossible-to-browse.patch,
> screenshot-1.png
>
>
> "Ranger User Sync" logs into Ranger multiple times a second. This is with:
> {code}
> ranger.usersync.source.impl.class=org.apache.ranger.unixusersync.process.UnixUserGroupBuilder
> ranger.usersync.unix.backend=nss
> {code}
> The high number and rate of these sessions makes it impossible to use the
> "Login Sessions" audit page:
> Further, it's adding a lot of extra requests and overhead to Ranger, Ranger
> User Sync, and the backing database (e.g. MySQL).
> *The service should re-use its session rather than continual logins.*
> !screenshot-1.png|width=640!
> {code}
> $ rpm -qa *usersync*
> ranger_2_6_4_0_91-usersync-0.7.0.2.6.4.0-91.x86_64
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (RANGER-2021) Ranger "Login Sessions" Audits impossible to browse due to 'rangerusersync'
[
https://issues.apache.org/jira/browse/RANGER-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikhil Purbhe updated RANGER-2021:
--
Attachment: RANGER-2021-RANGER-2064-Ranger-Usersync-should-use-c.patch
> Ranger "Login Sessions" Audits impossible to browse due to 'rangerusersync'
> ---
>
> Key: RANGER-2021
> URL: https://issues.apache.org/jira/browse/RANGER-2021
> Project: Ranger
> Issue Type: Bug
> Components: usersync
>Affects Versions: 0.7.0
>Reporter: Sean Roberts
>Assignee: Nikhil Purbhe
>Priority: Major
> Attachments:
> RANGER-2021-RANGER-2064-Ranger-Usersync-should-use-c.patch,
> RANGER-2021-Ranger-Login-Sessions-Audits-impossible-to-browse.patch,
> screenshot-1.png
>
>
> "Ranger User Sync" logs into Ranger multiple times a second. This is with:
> {code}
> ranger.usersync.source.impl.class=org.apache.ranger.unixusersync.process.UnixUserGroupBuilder
> ranger.usersync.unix.backend=nss
> {code}
> The high number and rate of these sessions makes it impossible to use the
> "Login Sessions" audit page:
> Further, it's adding a lot of extra requests and overhead to Ranger, Ranger
> User Sync, and the backing database (e.g. MySQL).
> *The service should re-use its session rather than continual logins.*
> !screenshot-1.png|width=640!
> {code}
> $ rpm -qa *usersync*
> ranger_2_6_4_0_91-usersync-0.7.0.2.6.4.0-91.x86_64
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (RANGER-2021) Ranger "Login Sessions" Audits impossible to browse due to 'rangerusersync'
[
https://issues.apache.org/jira/browse/RANGER-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikhil Purbhe updated RANGER-2021:
--
Attachment:
RANGER-2021-Ranger-Login-Sessions-Audits-impossible-to-browse.patch
> Ranger "Login Sessions" Audits impossible to browse due to 'rangerusersync'
> ---
>
> Key: RANGER-2021
> URL: https://issues.apache.org/jira/browse/RANGER-2021
> Project: Ranger
> Issue Type: Bug
> Components: usersync
>Affects Versions: 0.7.0
>Reporter: Sean Roberts
>Assignee: Nikhil Purbhe
>Priority: Major
> Attachments:
> RANGER-2021-Ranger-Login-Sessions-Audits-impossible-to-browse.patch,
> screenshot-1.png
>
>
> "Ranger User Sync" logs into Ranger multiple times a second. This is with:
> {code}
> ranger.usersync.source.impl.class=org.apache.ranger.unixusersync.process.UnixUserGroupBuilder
> ranger.usersync.unix.backend=nss
> {code}
> The high number and rate of these sessions makes it impossible to use the
> "Login Sessions" audit page:
> Further, it's adding a lot of extra requests and overhead to Ranger, Ranger
> User Sync, and the backing database (e.g. MySQL).
> *The service should re-use its session rather than continual logins.*
> !screenshot-1.png|width=640!
> {code}
> $ rpm -qa *usersync*
> ranger_2_6_4_0_91-usersync-0.7.0.2.6.4.0-91.x86_64
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (RANGER-2021) Ranger "Login Sessions" Audits impossible to browse due to 'rangerusersync'
[
https://issues.apache.org/jira/browse/RANGER-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated RANGER-2021:
-
Description:
"Ranger User Sync" logs into Ranger multiple times a second. This is with:
{code}
ranger.usersync.source.impl.class=org.apache.ranger.unixusersync.process.UnixUserGroupBuilder
ranger.usersync.unix.backend=nss
{code}
The high number and rate of these sessions makes it impossible to use the
"Login Sessions" audit page:
Further, it's adding a lot of extra requests and overhead to Ranger, Ranger
User Sync, and the backing database (e.g. MySQL).
*The service should re-use its session rather than continual logins.*
!screenshot-1.png|width=640!
{code}
$ rpm -qa *usersync*
ranger_2_6_4_0_91-usersync-0.7.0.2.6.4.0-91.x86_64
{code}
was:
"Ranger User Sync" logs into Ranger multiple times a second. This is with:
{code}
ranger.usersync.source.impl.class=org.apache.ranger.unixusersync.process.UnixUserGroupBuilder
ranger.usersync.unix.backend=nss
{code}
The high number and rate of these sessions makes it impossible to use the
"Login Sessions" audit page:
Further, it's adding a lot of extra requests and overhead to Ranger, Ranger
User Sync, and the backing database (e.g. MySQL).
*The service should re-use its session rather than continual logins.*
!screenshot-1.png|width=640!
{code}
MariaDB [ranger]> select count(*),DATE(create_time) as date from x_auth_sess
where login_id='rangerusersync' group by DATE(create_time) order by date desc
limit 10;
+--++
| count(*) | date |
+--++
| 3558 | 2018-03-14 |
| 8520 | 2018-03-13 |
| 8514 | 2018-03-12 |
| 8508 | 2018-03-11 |
| 8520 | 2018-03-10 |
| 8523 | 2018-03-09 |
| 8532 | 2018-03-08 |
| 8522 | 2018-03-07 |
| 8528 | 2018-03-06 |
| 8520 | 2018-03-05 |
+--++
10 rows in set (0.13 sec)
{code}
{code}
$ rpm -qa *usersync*
ranger_2_6_4_0_91-usersync-0.7.0.2.6.4.0-91.x86_64
{code}
> Ranger "Login Sessions" Audits impossible to browse due to 'rangerusersync'
> ---
>
> Key: RANGER-2021
> URL: https://issues.apache.org/jira/browse/RANGER-2021
> Project: Ranger
> Issue Type: Bug
> Components: usersync
>Affects Versions: 0.7.0
>Reporter: Sean Roberts
>Priority: Major
> Attachments: screenshot-1.png
>
>
> "Ranger User Sync" logs into Ranger multiple times a second. This is with:
> {code}
> ranger.usersync.source.impl.class=org.apache.ranger.unixusersync.process.UnixUserGroupBuilder
> ranger.usersync.unix.backend=nss
> {code}
> The high number and rate of these sessions makes it impossible to use the
> "Login Sessions" audit page:
> Further, it's adding a lot of extra requests and overhead to Ranger, Ranger
> User Sync, and the backing database (e.g. MySQL).
> *The service should re-use its session rather than continual logins.*
> !screenshot-1.png|width=640!
> {code}
> $ rpm -qa *usersync*
> ranger_2_6_4_0_91-usersync-0.7.0.2.6.4.0-91.x86_64
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (RANGER-2021) Ranger "Login Sessions" Audits impossible to browse due to 'rangerusersync'
[
https://issues.apache.org/jira/browse/RANGER-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated RANGER-2021:
-
Description:
"Ranger User Sync" logs into Ranger multiple times a second. This is with:
{code}
ranger.usersync.source.impl.class=org.apache.ranger.unixusersync.process.UnixUserGroupBuilder
ranger.usersync.unix.backend=nss
{code}
The high number and rate of these sessions makes it impossible to use the
"Login Sessions" audit page:
Further, it's adding a lot of extra requests and overhead to Ranger, Ranger
User Sync, and the backing database (e.g. MySQL).
*The service should re-use its session rather than continual logins.*
!screenshot-1.png|width=640!
{code}
MariaDB [ranger]> select count(*),DATE(create_time) as date from x_auth_sess
where login_id='rangerusersync' group by DATE(create_time) order by date desc
limit 10;
+--++
| count(*) | date |
+--++
| 3558 | 2018-03-14 |
| 8520 | 2018-03-13 |
| 8514 | 2018-03-12 |
| 8508 | 2018-03-11 |
| 8520 | 2018-03-10 |
| 8523 | 2018-03-09 |
| 8532 | 2018-03-08 |
| 8522 | 2018-03-07 |
| 8528 | 2018-03-06 |
| 8520 | 2018-03-05 |
+--++
10 rows in set (0.13 sec)
{code}
{code}
$ rpm -qa *usersync*
ranger_2_6_4_0_91-usersync-0.7.0.2.6.4.0-91.x86_64
{code}
was:
"Ranger User Sync" logs into Ranger multiple times a second. This is with:
{code}
ranger.usersync.source.impl.class=org.apache.ranger.unixusersync.process.UnixUserGroupBuilder
ranger.usersync.unix.backend=nss
{code}
The high number and rate of these sessions makes it impossible to use the
"Login Sessions" audit page:
Further, it's adding a lot of extra requests and overhead to Ranger, Ranger
User Sync, and the backing database (e.g. MySQL).
The service should re-use its session rather than continual logins.
!screenshot-1.png|width=640!
{code}
MariaDB [ranger]> select count(*),DATE(create_time) as date from x_auth_sess
where login_id='rangerusersync' group by DATE(create_time) order by date desc
limit 10;
+--++
| count(*) | date |
+--++
| 3558 | 2018-03-14 |
| 8520 | 2018-03-13 |
| 8514 | 2018-03-12 |
| 8508 | 2018-03-11 |
| 8520 | 2018-03-10 |
| 8523 | 2018-03-09 |
| 8532 | 2018-03-08 |
| 8522 | 2018-03-07 |
| 8528 | 2018-03-06 |
| 8520 | 2018-03-05 |
+--++
10 rows in set (0.13 sec)
{code}
{code}
$ rpm -qa *usersync*
ranger_2_6_4_0_91-usersync-0.7.0.2.6.4.0-91.x86_64
{code}
> Ranger "Login Sessions" Audits impossible to browse due to 'rangerusersync'
> ---
>
> Key: RANGER-2021
> URL: https://issues.apache.org/jira/browse/RANGER-2021
> Project: Ranger
> Issue Type: Bug
> Components: usersync
>Affects Versions: 0.7.0
>Reporter: Sean Roberts
>Priority: Major
> Attachments: screenshot-1.png
>
>
> "Ranger User Sync" logs into Ranger multiple times a second. This is with:
> {code}
> ranger.usersync.source.impl.class=org.apache.ranger.unixusersync.process.UnixUserGroupBuilder
> ranger.usersync.unix.backend=nss
> {code}
> The high number and rate of these sessions makes it impossible to use the
> "Login Sessions" audit page:
> Further, it's adding a lot of extra requests and overhead to Ranger, Ranger
> User Sync, and the backing database (e.g. MySQL).
> *The service should re-use its session rather than continual logins.*
> !screenshot-1.png|width=640!
> {code}
> MariaDB [ranger]> select count(*),DATE(create_time) as date from x_auth_sess
> where login_id='rangerusersync' group by DATE(create_time) order by date desc
> limit 10;
> +--++
> | count(*) | date |
> +--++
> | 3558 | 2018-03-14 |
> | 8520 | 2018-03-13 |
> | 8514 | 2018-03-12 |
> | 8508 | 2018-03-11 |
> | 8520 | 2018-03-10 |
> | 8523 | 2018-03-09 |
> | 8532 | 2018-03-08 |
> | 8522 | 2018-03-07 |
> | 8528 | 2018-03-06 |
> | 8520 | 2018-03-05 |
> +--++
> 10 rows in set (0.13 sec)
> {code}
> {code}
> $ rpm -qa *usersync*
> ranger_2_6_4_0_91-usersync-0.7.0.2.6.4.0-91.x86_64
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (RANGER-2021) Ranger "Login Sessions" Audits impossible to browse due to 'rangerusersync'
[
https://issues.apache.org/jira/browse/RANGER-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated RANGER-2021:
-
Description:
"Ranger User Sync" logs into Ranger multiple times a second. This is with:
{code}
ranger.usersync.source.impl.class=org.apache.ranger.unixusersync.process.UnixUserGroupBuilder
ranger.usersync.unix.backend=nss
{code}
The high number and rate of these sessions makes it impossible to use the
"Login Sessions" audit page:
Further, it's adding a lot of extra requests and overhead to Ranger, Ranger
User Sync, and the backing database (e.g. MySQL).
The service should re-use its session rather than continual logins.
!screenshot-1.png|thumbnail!
{code}
MariaDB [ranger]> select count(*),DATE(create_time) as date from x_auth_sess
where login_id='rangerusersync' group by DATE(create_time) order by date desc
limit 10;
+--++
| count(*) | date |
+--++
| 3558 | 2018-03-14 |
| 8520 | 2018-03-13 |
| 8514 | 2018-03-12 |
| 8508 | 2018-03-11 |
| 8520 | 2018-03-10 |
| 8523 | 2018-03-09 |
| 8532 | 2018-03-08 |
| 8522 | 2018-03-07 |
| 8528 | 2018-03-06 |
| 8520 | 2018-03-05 |
+--++
10 rows in set (0.13 sec)
{code}
{code}
$ rpm -qa *usersync*
ranger_2_6_4_0_91-usersync-0.7.0.2.6.4.0-91.x86_64
{code}
was:
"Ranger User Sync" logs into Ranger multiple times a second. This is with:
{code}
ranger.usersync.source.impl.class=org.apache.ranger.unixusersync.process.UnixUserGroupBuilder
ranger.usersync.unix.backend=nss
{code}
The high number and rate of these sessions makes it impossible to use the
"Login Sessions" audit page:
Further, it's adding a lot of extra requests and overhead to Ranger, Ranger
User Sync, and the backing database (e.g. MySQL).
The service should re-use its session rather than continual logins.
!screenshot-1.png|thumbnail!
{code}
MariaDB [ranger]> select count(*),DATE(create_time) as date from x_auth_sess
where login_id='rangerusersync' group by DATE(create_time) order by date desc
limit 10;
+--++
| count(*) | date |
+--++
| 3558 | 2018-03-14 |
| 8520 | 2018-03-13 |
| 8514 | 2018-03-12 |
| 8508 | 2018-03-11 |
| 8520 | 2018-03-10 |
| 8523 | 2018-03-09 |
| 8532 | 2018-03-08 |
| 8522 | 2018-03-07 |
| 8528 | 2018-03-06 |
| 8520 | 2018-03-05 |
+--++
10 rows in set (0.13 sec)
{code}
{code}
$ rpm -qa *usersync*
ranger_2_6_4_0_91-usersync-0.7.0.2.6.4.0-91.x86_64
{code}
> Ranger "Login Sessions" Audits impossible to browse due to 'rangerusersync'
> ---
>
> Key: RANGER-2021
> URL: https://issues.apache.org/jira/browse/RANGER-2021
> Project: Ranger
> Issue Type: Bug
> Components: usersync
>Affects Versions: 0.7.0
>Reporter: Sean Roberts
>Priority: Major
> Attachments: screenshot-1.png
>
>
> "Ranger User Sync" logs into Ranger multiple times a second. This is with:
> {code}
> ranger.usersync.source.impl.class=org.apache.ranger.unixusersync.process.UnixUserGroupBuilder
> ranger.usersync.unix.backend=nss
> {code}
> The high number and rate of these sessions makes it impossible to use the
> "Login Sessions" audit page:
> Further, it's adding a lot of extra requests and overhead to Ranger, Ranger
> User Sync, and the backing database (e.g. MySQL).
> The service should re-use its session rather than continual logins.
> !screenshot-1.png|thumbnail!
> {code}
> MariaDB [ranger]> select count(*),DATE(create_time) as date from x_auth_sess
> where login_id='rangerusersync' group by DATE(create_time) order by date desc
> limit 10;
> +--++
> | count(*) | date |
> +--++
> | 3558 | 2018-03-14 |
> | 8520 | 2018-03-13 |
> | 8514 | 2018-03-12 |
> | 8508 | 2018-03-11 |
> | 8520 | 2018-03-10 |
> | 8523 | 2018-03-09 |
> | 8532 | 2018-03-08 |
> | 8522 | 2018-03-07 |
> | 8528 | 2018-03-06 |
> | 8520 | 2018-03-05 |
> +--++
> 10 rows in set (0.13 sec)
> {code}
> {code}
> $ rpm -qa *usersync*
> ranger_2_6_4_0_91-usersync-0.7.0.2.6.4.0-91.x86_64
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (RANGER-2021) Ranger "Login Sessions" Audits impossible to browse due to 'rangerusersync'
[
https://issues.apache.org/jira/browse/RANGER-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated RANGER-2021:
-
Description:
"Ranger User Sync" logs into Ranger multiple times a second. This is with:
{code}
ranger.usersync.source.impl.class=org.apache.ranger.unixusersync.process.UnixUserGroupBuilder
ranger.usersync.unix.backend=nss
{code}
The high number and rate of these sessions makes it impossible to use the
"Login Sessions" audit page:
Further, it's adding a lot of extra requests and overhead to Ranger, Ranger
User Sync, and the backing database (e.g. MySQL).
The service should re-use its session rather than continual logins.
!screenshot-1.png|with=640!
{code}
MariaDB [ranger]> select count(*),DATE(create_time) as date from x_auth_sess
where login_id='rangerusersync' group by DATE(create_time) order by date desc
limit 10;
+--++
| count(*) | date |
+--++
| 3558 | 2018-03-14 |
| 8520 | 2018-03-13 |
| 8514 | 2018-03-12 |
| 8508 | 2018-03-11 |
| 8520 | 2018-03-10 |
| 8523 | 2018-03-09 |
| 8532 | 2018-03-08 |
| 8522 | 2018-03-07 |
| 8528 | 2018-03-06 |
| 8520 | 2018-03-05 |
+--++
10 rows in set (0.13 sec)
{code}
{code}
$ rpm -qa *usersync*
ranger_2_6_4_0_91-usersync-0.7.0.2.6.4.0-91.x86_64
{code}
was:
"Ranger User Sync" logs into Ranger multiple times a second. This is with:
{code}
ranger.usersync.source.impl.class=org.apache.ranger.unixusersync.process.UnixUserGroupBuilder
ranger.usersync.unix.backend=nss
{code}
The high number and rate of these sessions makes it impossible to use the
"Login Sessions" audit page:
Further, it's adding a lot of extra requests and overhead to Ranger, Ranger
User Sync, and the backing database (e.g. MySQL).
The service should re-use its session rather than continual logins.
!screenshot-1.png|thumbnail!
{code}
MariaDB [ranger]> select count(*),DATE(create_time) as date from x_auth_sess
where login_id='rangerusersync' group by DATE(create_time) order by date desc
limit 10;
+--++
| count(*) | date |
+--++
| 3558 | 2018-03-14 |
| 8520 | 2018-03-13 |
| 8514 | 2018-03-12 |
| 8508 | 2018-03-11 |
| 8520 | 2018-03-10 |
| 8523 | 2018-03-09 |
| 8532 | 2018-03-08 |
| 8522 | 2018-03-07 |
| 8528 | 2018-03-06 |
| 8520 | 2018-03-05 |
+--++
10 rows in set (0.13 sec)
{code}
{code}
$ rpm -qa *usersync*
ranger_2_6_4_0_91-usersync-0.7.0.2.6.4.0-91.x86_64
{code}
> Ranger "Login Sessions" Audits impossible to browse due to 'rangerusersync'
> ---
>
> Key: RANGER-2021
> URL: https://issues.apache.org/jira/browse/RANGER-2021
> Project: Ranger
> Issue Type: Bug
> Components: usersync
>Affects Versions: 0.7.0
>Reporter: Sean Roberts
>Priority: Major
> Attachments: screenshot-1.png
>
>
> "Ranger User Sync" logs into Ranger multiple times a second. This is with:
> {code}
> ranger.usersync.source.impl.class=org.apache.ranger.unixusersync.process.UnixUserGroupBuilder
> ranger.usersync.unix.backend=nss
> {code}
> The high number and rate of these sessions makes it impossible to use the
> "Login Sessions" audit page:
> Further, it's adding a lot of extra requests and overhead to Ranger, Ranger
> User Sync, and the backing database (e.g. MySQL).
> The service should re-use its session rather than continual logins.
> !screenshot-1.png|with=640!
> {code}
> MariaDB [ranger]> select count(*),DATE(create_time) as date from x_auth_sess
> where login_id='rangerusersync' group by DATE(create_time) order by date desc
> limit 10;
> +--++
> | count(*) | date |
> +--++
> | 3558 | 2018-03-14 |
> | 8520 | 2018-03-13 |
> | 8514 | 2018-03-12 |
> | 8508 | 2018-03-11 |
> | 8520 | 2018-03-10 |
> | 8523 | 2018-03-09 |
> | 8532 | 2018-03-08 |
> | 8522 | 2018-03-07 |
> | 8528 | 2018-03-06 |
> | 8520 | 2018-03-05 |
> +--++
> 10 rows in set (0.13 sec)
> {code}
> {code}
> $ rpm -qa *usersync*
> ranger_2_6_4_0_91-usersync-0.7.0.2.6.4.0-91.x86_64
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (RANGER-2021) Ranger "Login Sessions" Audits impossible to browse due to 'rangerusersync'
[
https://issues.apache.org/jira/browse/RANGER-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated RANGER-2021:
-
Description:
"Ranger User Sync" logs into Ranger multiple times a second. This is with:
{code}
ranger.usersync.source.impl.class=org.apache.ranger.unixusersync.process.UnixUserGroupBuilder
ranger.usersync.unix.backend=nss
{code}
The high number and rate of these sessions makes it impossible to use the
"Login Sessions" audit page:
Further, it's adding a lot of extra requests and overhead to Ranger, Ranger
User Sync, and the backing database (e.g. MySQL).
The service should re-use its session rather than continual logins.
!screenshot-1.png|width=640!
{code}
MariaDB [ranger]> select count(*),DATE(create_time) as date from x_auth_sess
where login_id='rangerusersync' group by DATE(create_time) order by date desc
limit 10;
+--++
| count(*) | date |
+--++
| 3558 | 2018-03-14 |
| 8520 | 2018-03-13 |
| 8514 | 2018-03-12 |
| 8508 | 2018-03-11 |
| 8520 | 2018-03-10 |
| 8523 | 2018-03-09 |
| 8532 | 2018-03-08 |
| 8522 | 2018-03-07 |
| 8528 | 2018-03-06 |
| 8520 | 2018-03-05 |
+--++
10 rows in set (0.13 sec)
{code}
{code}
$ rpm -qa *usersync*
ranger_2_6_4_0_91-usersync-0.7.0.2.6.4.0-91.x86_64
{code}
was:
"Ranger User Sync" logs into Ranger multiple times a second. This is with:
{code}
ranger.usersync.source.impl.class=org.apache.ranger.unixusersync.process.UnixUserGroupBuilder
ranger.usersync.unix.backend=nss
{code}
The high number and rate of these sessions makes it impossible to use the
"Login Sessions" audit page:
Further, it's adding a lot of extra requests and overhead to Ranger, Ranger
User Sync, and the backing database (e.g. MySQL).
The service should re-use its session rather than continual logins.
!screenshot-1.png|with=640!
{code}
MariaDB [ranger]> select count(*),DATE(create_time) as date from x_auth_sess
where login_id='rangerusersync' group by DATE(create_time) order by date desc
limit 10;
+--++
| count(*) | date |
+--++
| 3558 | 2018-03-14 |
| 8520 | 2018-03-13 |
| 8514 | 2018-03-12 |
| 8508 | 2018-03-11 |
| 8520 | 2018-03-10 |
| 8523 | 2018-03-09 |
| 8532 | 2018-03-08 |
| 8522 | 2018-03-07 |
| 8528 | 2018-03-06 |
| 8520 | 2018-03-05 |
+--++
10 rows in set (0.13 sec)
{code}
{code}
$ rpm -qa *usersync*
ranger_2_6_4_0_91-usersync-0.7.0.2.6.4.0-91.x86_64
{code}
> Ranger "Login Sessions" Audits impossible to browse due to 'rangerusersync'
> ---
>
> Key: RANGER-2021
> URL: https://issues.apache.org/jira/browse/RANGER-2021
> Project: Ranger
> Issue Type: Bug
> Components: usersync
>Affects Versions: 0.7.0
>Reporter: Sean Roberts
>Priority: Major
> Attachments: screenshot-1.png
>
>
> "Ranger User Sync" logs into Ranger multiple times a second. This is with:
> {code}
> ranger.usersync.source.impl.class=org.apache.ranger.unixusersync.process.UnixUserGroupBuilder
> ranger.usersync.unix.backend=nss
> {code}
> The high number and rate of these sessions makes it impossible to use the
> "Login Sessions" audit page:
> Further, it's adding a lot of extra requests and overhead to Ranger, Ranger
> User Sync, and the backing database (e.g. MySQL).
> The service should re-use its session rather than continual logins.
> !screenshot-1.png|width=640!
> {code}
> MariaDB [ranger]> select count(*),DATE(create_time) as date from x_auth_sess
> where login_id='rangerusersync' group by DATE(create_time) order by date desc
> limit 10;
> +--++
> | count(*) | date |
> +--++
> | 3558 | 2018-03-14 |
> | 8520 | 2018-03-13 |
> | 8514 | 2018-03-12 |
> | 8508 | 2018-03-11 |
> | 8520 | 2018-03-10 |
> | 8523 | 2018-03-09 |
> | 8532 | 2018-03-08 |
> | 8522 | 2018-03-07 |
> | 8528 | 2018-03-06 |
> | 8520 | 2018-03-05 |
> +--++
> 10 rows in set (0.13 sec)
> {code}
> {code}
> $ rpm -qa *usersync*
> ranger_2_6_4_0_91-usersync-0.7.0.2.6.4.0-91.x86_64
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (RANGER-2021) Ranger "Login Sessions" Audits impossible to browse due to 'rangerusersync'
[
https://issues.apache.org/jira/browse/RANGER-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated RANGER-2021:
-
Description:
"Ranger User Sync" logs into Ranger multiple times a second. This is with:
{code}
ranger.usersync.source.impl.class=org.apache.ranger.unixusersync.process.UnixUserGroupBuilder
ranger.usersync.unix.backend=nss
{code}
The high number and rate of these sessions makes it impossible to use the
"Login Sessions" audit page:
Further, it's adding a lot of extra requests and overhead to Ranger, Ranger
User Sync, and the backing database (e.g. MySQL).
The service should re-use its session rather than continual logins.
!screenshot-1.png|thumbnail!
{code}
MariaDB [ranger]> select count(*),DATE(create_time) as date from x_auth_sess
where login_id='rangerusersync' group by DATE(create_time) order by date desc
limit 10;
+--++
| count(*) | date |
+--++
| 3558 | 2018-03-14 |
| 8520 | 2018-03-13 |
| 8514 | 2018-03-12 |
| 8508 | 2018-03-11 |
| 8520 | 2018-03-10 |
| 8523 | 2018-03-09 |
| 8532 | 2018-03-08 |
| 8522 | 2018-03-07 |
| 8528 | 2018-03-06 |
| 8520 | 2018-03-05 |
+--++
10 rows in set (0.13 sec)
{code}
{code}
$ rpm -qa *usersync*
ranger_2_6_4_0_91-usersync-0.7.0.2.6.4.0-91.x86_64
{code}
was:
"Ranger User Sync" logs into Ranger multiple times a second. This is with:
{code}
ranger.usersync.source.impl.class=org.apache.ranger.unixusersync.process.UnixUserGroupBuilder
ranger.usersync.unix.backend=nss
{code}
The high number and rate of these sessions makes it impossible to use the
"Login Sessions" audit page:
Further, it's adding a lot of extra requests and overhead to Ranger, Ranger
User Sync, and the backing database (e.g. MySQL).
The service should re-use its session rather than continual logins.
!screenshot-1.png!thumbnail!
{code}
MariaDB [ranger]> select count(*),DATE(create_time) as date from x_auth_sess
where login_id='rangerusersync' group by DATE(create_time) order by date desc
limit 10;
+--++
| count(*) | date |
+--++
| 3558 | 2018-03-14 |
| 8520 | 2018-03-13 |
| 8514 | 2018-03-12 |
| 8508 | 2018-03-11 |
| 8520 | 2018-03-10 |
| 8523 | 2018-03-09 |
| 8532 | 2018-03-08 |
| 8522 | 2018-03-07 |
| 8528 | 2018-03-06 |
| 8520 | 2018-03-05 |
+--++
10 rows in set (0.13 sec)
{code}
{code}
$ rpm -qa *usersync*
ranger_2_6_4_0_91-usersync-0.7.0.2.6.4.0-91.x86_64
{code}
> Ranger "Login Sessions" Audits impossible to browse due to 'rangerusersync'
> ---
>
> Key: RANGER-2021
> URL: https://issues.apache.org/jira/browse/RANGER-2021
> Project: Ranger
> Issue Type: Bug
> Components: usersync
>Affects Versions: 0.7.0
>Reporter: Sean Roberts
>Priority: Major
> Attachments: screenshot-1.png
>
>
> "Ranger User Sync" logs into Ranger multiple times a second. This is with:
> {code}
> ranger.usersync.source.impl.class=org.apache.ranger.unixusersync.process.UnixUserGroupBuilder
> ranger.usersync.unix.backend=nss
> {code}
> The high number and rate of these sessions makes it impossible to use the
> "Login Sessions" audit page:
> Further, it's adding a lot of extra requests and overhead to Ranger, Ranger
> User Sync, and the backing database (e.g. MySQL).
> The service should re-use its session rather than continual logins.
> !screenshot-1.png|thumbnail!
> {code}
> MariaDB [ranger]> select count(*),DATE(create_time) as date from x_auth_sess
> where login_id='rangerusersync' group by DATE(create_time) order by date desc
> limit 10;
> +--++
> | count(*) | date |
> +--++
> | 3558 | 2018-03-14 |
> | 8520 | 2018-03-13 |
> | 8514 | 2018-03-12 |
> | 8508 | 2018-03-11 |
> | 8520 | 2018-03-10 |
> | 8523 | 2018-03-09 |
> | 8532 | 2018-03-08 |
> | 8522 | 2018-03-07 |
> | 8528 | 2018-03-06 |
> | 8520 | 2018-03-05 |
> +--++
> 10 rows in set (0.13 sec)
> {code}
> {code}
> $ rpm -qa *usersync*
> ranger_2_6_4_0_91-usersync-0.7.0.2.6.4.0-91.x86_64
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (RANGER-2021) Ranger "Login Sessions" Audits impossible to browse due to 'rangerusersync'
[
https://issues.apache.org/jira/browse/RANGER-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated RANGER-2021:
-
Description:
"Ranger User Sync" logs into Ranger multiple times a second. This is with:
{code}
ranger.usersync.source.impl.class=org.apache.ranger.unixusersync.process.UnixUserGroupBuilder
ranger.usersync.unix.backend=nss
{code}
The high number and rate of these sessions makes it impossible to use the
"Login Sessions" audit page:
Further, it's adding a lot of extra requests and overhead to Ranger, Ranger
User Sync, and the backing database (e.g. MySQL).
The service should re-use its session rather than continual logins.
!screenshot-1.png!thumbnail!
{code}
MariaDB [ranger]> select count(*),DATE(create_time) as date from x_auth_sess
where login_id='rangerusersync' group by DATE(create_time) order by date desc
limit 10;
+--++
| count(*) | date |
+--++
| 3558 | 2018-03-14 |
| 8520 | 2018-03-13 |
| 8514 | 2018-03-12 |
| 8508 | 2018-03-11 |
| 8520 | 2018-03-10 |
| 8523 | 2018-03-09 |
| 8532 | 2018-03-08 |
| 8522 | 2018-03-07 |
| 8528 | 2018-03-06 |
| 8520 | 2018-03-05 |
+--++
10 rows in set (0.13 sec)
{code}
{code}
$ rpm -qa *usersync*
ranger_2_6_4_0_91-usersync-0.7.0.2.6.4.0-91.x86_64
{code}
was:
"Ranger User Sync" logs into Ranger multiple times a second. This is with unix
sync with PAM.
The high number and rate of these sessions makes it impossible to use the
"Login Sessions" audit page:
Further, it's adding a lot of extra requests and overhead to Ranger, Ranger
User Sync, and the backing database (e.g. MySQL).
The service should re-use its session rather than continual logins.
{code}
MariaDB [ranger]> select count(*),DATE(create_time) as date from x_auth_sess
where login_id='rangerusersync' group by DATE(create_time) order by date desc
limit 10;
+--++
| count(*) | date |
+--++
| 3558 | 2018-03-14 |
| 8520 | 2018-03-13 |
| 8514 | 2018-03-12 |
| 8508 | 2018-03-11 |
| 8520 | 2018-03-10 |
| 8523 | 2018-03-09 |
| 8532 | 2018-03-08 |
| 8522 | 2018-03-07 |
| 8528 | 2018-03-06 |
| 8520 | 2018-03-05 |
+--++
10 rows in set (0.13 sec)
{code}
!screenshot-1.png!
{code}
$ rpm -qa *usersync*
ranger_2_6_4_0_91-usersync-0.7.0.2.6.4.0-91.x86_64
{code}
> Ranger "Login Sessions" Audits impossible to browse due to 'rangerusersync'
> ---
>
> Key: RANGER-2021
> URL: https://issues.apache.org/jira/browse/RANGER-2021
> Project: Ranger
> Issue Type: Bug
> Components: usersync
>Affects Versions: 0.7.0
>Reporter: Sean Roberts
>Priority: Major
> Attachments: screenshot-1.png
>
>
> "Ranger User Sync" logs into Ranger multiple times a second. This is with:
> {code}
> ranger.usersync.source.impl.class=org.apache.ranger.unixusersync.process.UnixUserGroupBuilder
> ranger.usersync.unix.backend=nss
> {code}
> The high number and rate of these sessions makes it impossible to use the
> "Login Sessions" audit page:
> Further, it's adding a lot of extra requests and overhead to Ranger, Ranger
> User Sync, and the backing database (e.g. MySQL).
> The service should re-use its session rather than continual logins.
> !screenshot-1.png!thumbnail!
> {code}
> MariaDB [ranger]> select count(*),DATE(create_time) as date from x_auth_sess
> where login_id='rangerusersync' group by DATE(create_time) order by date desc
> limit 10;
> +--++
> | count(*) | date |
> +--++
> | 3558 | 2018-03-14 |
> | 8520 | 2018-03-13 |
> | 8514 | 2018-03-12 |
> | 8508 | 2018-03-11 |
> | 8520 | 2018-03-10 |
> | 8523 | 2018-03-09 |
> | 8532 | 2018-03-08 |
> | 8522 | 2018-03-07 |
> | 8528 | 2018-03-06 |
> | 8520 | 2018-03-05 |
> +--++
> 10 rows in set (0.13 sec)
> {code}
> {code}
> $ rpm -qa *usersync*
> ranger_2_6_4_0_91-usersync-0.7.0.2.6.4.0-91.x86_64
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (RANGER-2021) Ranger "Login Sessions" Audits impossible to browse due to 'rangerusersync'
[
https://issues.apache.org/jira/browse/RANGER-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated RANGER-2021:
-
Description:
"Ranger User Sync" logs into Ranger multiple times a second. This is with unix
sync with PAM.
The high number and rate of these sessions makes it impossible to use the
"Login Sessions" audit page:
Further, it's adding a lot of extra requests and overhead to Ranger, Ranger
User Sync, and the backing database (e.g. MySQL).
The service should re-use its session rather than continual logins.
{code}
MariaDB [ranger]> select count(*),DATE(create_time) as date from x_auth_sess
where login_id='rangerusersync' group by DATE(create_time) order by date desc
limit 10;
+--++
| count(*) | date |
+--++
| 3558 | 2018-03-14 |
| 8520 | 2018-03-13 |
| 8514 | 2018-03-12 |
| 8508 | 2018-03-11 |
| 8520 | 2018-03-10 |
| 8523 | 2018-03-09 |
| 8532 | 2018-03-08 |
| 8522 | 2018-03-07 |
| 8528 | 2018-03-06 |
| 8520 | 2018-03-05 |
+--++
10 rows in set (0.13 sec)
{code}
!screenshot-1.png!
{code}
$ rpm -qa *usersync*
ranger_2_6_4_0_91-usersync-0.7.0.2.6.4.0-91.x86_64
{code}
was:
"Ranger User Sync" logs into Ranger multiple times a second.
The high number and rate of these sessions makes it impossible to use the
"Login Sessions" audit page:
!screenshot-1.png!
Further, it's adding a lot of extra requests and overhead to Ranger, Ranger
User Sync, and the backing database (e.g. MySQL).
The service should re-use its session rather than continual logins.
{code}
$ rpm -qa *usersync*
ranger_2_6_4_0_91-usersync-0.7.0.2.6.4.0-91.x86_64
{code}
> Ranger "Login Sessions" Audits impossible to browse due to 'rangerusersync'
> ---
>
> Key: RANGER-2021
> URL: https://issues.apache.org/jira/browse/RANGER-2021
> Project: Ranger
> Issue Type: Bug
> Components: usersync
>Affects Versions: 0.7.0
>Reporter: Sean Roberts
>Priority: Major
> Attachments: screenshot-1.png
>
>
> "Ranger User Sync" logs into Ranger multiple times a second. This is with
> unix sync with PAM.
> The high number and rate of these sessions makes it impossible to use the
> "Login Sessions" audit page:
> Further, it's adding a lot of extra requests and overhead to Ranger, Ranger
> User Sync, and the backing database (e.g. MySQL).
> The service should re-use its session rather than continual logins.
> {code}
> MariaDB [ranger]> select count(*),DATE(create_time) as date from x_auth_sess
> where login_id='rangerusersync' group by DATE(create_time) order by date desc
> limit 10;
> +--++
> | count(*) | date |
> +--++
> | 3558 | 2018-03-14 |
> | 8520 | 2018-03-13 |
> | 8514 | 2018-03-12 |
> | 8508 | 2018-03-11 |
> | 8520 | 2018-03-10 |
> | 8523 | 2018-03-09 |
> | 8532 | 2018-03-08 |
> | 8522 | 2018-03-07 |
> | 8528 | 2018-03-06 |
> | 8520 | 2018-03-05 |
> +--++
> 10 rows in set (0.13 sec)
> {code}
> !screenshot-1.png!
> {code}
> $ rpm -qa *usersync*
> ranger_2_6_4_0_91-usersync-0.7.0.2.6.4.0-91.x86_64
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (RANGER-2021) Ranger "Login Sessions" Audits impossible to browse due to 'rangerusersync'
[
https://issues.apache.org/jira/browse/RANGER-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated RANGER-2021:
-
Description:
"Ranger User Sync" logs into Ranger multiple times a second.
The high number and rate of these sessions makes it impossible to use the
"Login Sessions" audit page:
!screenshot-1.png!
Further, it's adding a lot of extra requests and overhead to Ranger, Ranger
User Sync, and the backing database (e.g. MySQL).
The service should re-use its session rather than continual logins.
{code}
$ rpm -qa *usersync*
ranger_2_6_4_0_91-usersync-0.7.0.2.6.4.0-91.x86_64
{code}
was:
"Ranger User Sync" logs into Ranger multiple times a second.
The high number and rate of these sessions makes it impossible to use the
"Login Sessions" audit page.
Further, it's adding a lot of extra requests and overhead to Ranger, Ranger
User Sync, and the backing database (e.g. MySQL).
The service should re-use its session rather than continual logins.
{code}
$ rpm -qa *usersync*
ranger_2_6_4_0_91-usersync-0.7.0.2.6.4.0-91.x86_64
{code}
> Ranger "Login Sessions" Audits impossible to browse due to 'rangerusersync'
> ---
>
> Key: RANGER-2021
> URL: https://issues.apache.org/jira/browse/RANGER-2021
> Project: Ranger
> Issue Type: Bug
> Components: usersync
>Affects Versions: 0.7.0
>Reporter: Sean Roberts
>Priority: Major
> Attachments: screenshot-1.png
>
>
> "Ranger User Sync" logs into Ranger multiple times a second.
> The high number and rate of these sessions makes it impossible to use the
> "Login Sessions" audit page:
> !screenshot-1.png!
> Further, it's adding a lot of extra requests and overhead to Ranger, Ranger
> User Sync, and the backing database (e.g. MySQL).
> The service should re-use its session rather than continual logins.
> {code}
> $ rpm -qa *usersync*
> ranger_2_6_4_0_91-usersync-0.7.0.2.6.4.0-91.x86_64
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (RANGER-2021) Ranger "Login Sessions" Audits impossible to browse due to 'rangerusersync'
[
https://issues.apache.org/jira/browse/RANGER-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated RANGER-2021:
-
Attachment: screenshot-1.png
> Ranger "Login Sessions" Audits impossible to browse due to 'rangerusersync'
> ---
>
> Key: RANGER-2021
> URL: https://issues.apache.org/jira/browse/RANGER-2021
> Project: Ranger
> Issue Type: Bug
> Components: usersync
>Affects Versions: 0.7.0
>Reporter: Sean Roberts
>Priority: Major
> Attachments: screenshot-1.png
>
>
> "Ranger User Sync" logs into Ranger multiple times a second.
> The high number and rate of these sessions makes it impossible to use the
> "Login Sessions" audit page.
> Further, it's adding a lot of extra requests and overhead to Ranger, Ranger
> User Sync, and the backing database (e.g. MySQL).
> The service should re-use its session rather than continual logins.
> {code}
> $ rpm -qa *usersync*
> ranger_2_6_4_0_91-usersync-0.7.0.2.6.4.0-91.x86_64
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
