falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pragya Mittal (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (FALCON-1514) Incorrect logging while submitting cluster
Date Wed, 07 Oct 2015 05:37:26 GMT

     [ https://issues.apache.org/jira/browse/FALCON-1514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Pragya Mittal updated FALCON-1514:
----------------------------------
    Description: 
When cluster entity is submitted via prism/server, logs say the following :
{code}
2015-10-07 05:33:19,430 INFO  - [9959671@qtp-366590980-417 - 0bb0452f-1751-4017-a776-c6301aa737d4:pragya:POST//entities/submit/cluster]
~ Parsed Entity: A4dcc0afc-926620cf (EntityParser:94)
2015-10-07 05:33:19,431 INFO  - [9959671@qtp-366590980-417 - 0bb0452f-1751-4017-a776-c6301aa737d4:pragya:POST//entities/submit/cluster]
~ Lock obtained for schedule/update of (cluster) A4dcc0afc-926620cf by 9959671@qtp-366590980-417
- 0bb0452f-1751-4017-a776-c6301aa737d4 (MemoryLocks:54)
2015-10-07 05:33:19,431 INFO  - [9959671@qtp-366590980-417 - 0bb0452f-1751-4017-a776-c6301aa737d4:pragya:POST//entities/submit/cluster]
~ Successfully released lock for (cluster) A4dcc0afc-926620cf by 9959671@qtp-366590980-417
- 0bb0452f-1751-4017-a776-c6301aa737d4 (MemoryLocks:70)
2015-10-07 05:33:19,431 INFO  - [9959671@qtp-366590980-417 - 0bb0452f-1751-4017-a776-c6301aa737d4:pragya:POST//entities/submit/cluster]
~ All update locks released for A4dcc0afc-926620cf (AbstractEntityManager:357)

{code}

As the logs suggest, lock is obtained for schedule/update of cluster which is not very intuitive.

> Incorrect logging while submitting cluster
> ------------------------------------------
>
>                 Key: FALCON-1514
>                 URL: https://issues.apache.org/jira/browse/FALCON-1514
>             Project: Falcon
>          Issue Type: Bug
>          Components: prism
>    Affects Versions: 0.8
>            Reporter: Pragya Mittal
>
> When cluster entity is submitted via prism/server, logs say the following :
> {code}
> 2015-10-07 05:33:19,430 INFO  - [9959671@qtp-366590980-417 - 0bb0452f-1751-4017-a776-c6301aa737d4:pragya:POST//entities/submit/cluster]
~ Parsed Entity: A4dcc0afc-926620cf (EntityParser:94)
> 2015-10-07 05:33:19,431 INFO  - [9959671@qtp-366590980-417 - 0bb0452f-1751-4017-a776-c6301aa737d4:pragya:POST//entities/submit/cluster]
~ Lock obtained for schedule/update of (cluster) A4dcc0afc-926620cf by 9959671@qtp-366590980-417
- 0bb0452f-1751-4017-a776-c6301aa737d4 (MemoryLocks:54)
> 2015-10-07 05:33:19,431 INFO  - [9959671@qtp-366590980-417 - 0bb0452f-1751-4017-a776-c6301aa737d4:pragya:POST//entities/submit/cluster]
~ Successfully released lock for (cluster) A4dcc0afc-926620cf by 9959671@qtp-366590980-417
- 0bb0452f-1751-4017-a776-c6301aa737d4 (MemoryLocks:70)
> 2015-10-07 05:33:19,431 INFO  - [9959671@qtp-366590980-417 - 0bb0452f-1751-4017-a776-c6301aa737d4:pragya:POST//entities/submit/cluster]
~ All update locks released for A4dcc0afc-926620cf (AbstractEntityManager:357)
> {code}
> As the logs suggest, lock is obtained for schedule/update of cluster which is not very
intuitive.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message