Re: Atlas not working for complex hive query on single node

2017-08-15 Thread Vineet Mishra
It was a simple CTAS Query,

create table final_table as select a.* from table_a a inner join table_b b
on a.id=b.id

Where table_a and table_b just had a few records.

On Mon, Aug 14, 2017 at 6:01 AM, Madhan Neethiraj <mad...@apache.org> wrote:

> Vineet,
>
>
>
> It is not clear what might cause this error. To investigate this issue
> further, can you send the SQL statements that lead to this error?
>
>
>
> Thanks,
>
> Madhan
>
>
>
>
>
>
>
>
>
> *From: *Vineet Mishra <clearmido...@gmail.com>
> *Reply-To: *"user@atlas.apache.org" <user@atlas.apache.org>
> *Date: *Wednesday, August 9, 2017 at 3:45 AM
> *To: *"user@atlas.apache.org" <user@atlas.apache.org>
> *Subject: *Re: Atlas not working for complex hive query on single node
>
>
>
> Hi Guys,
>
>
>
> Any update on this?
>
>
>
> Caused by: com.sleepycat.je.LockTimeoutException: (JE 5.0.73) Lock
> expired. Locker 768997492 3544_NotificationHookConsumer thread-0_Txn:
> waited for lock on database=edgestore LockAddr:1860143233 LSN=0x0/0xc8613
> type=WRITE grant=WAIT_PROMOTION timeoutMillis=500 startTime=1502275039421
> endTime=1502275039921
>
> Owners: [, ]
>
> Waiters: []
>
> Transaction 768997492 3544_NotificationHookConsumer thread-0_Txn owns
> LockAddr:1860143233 
>
> Transaction 768997492 3544_NotificationHookConsumer thread-0_Txn waits for
> LockAddr:1860143233
>
>
>
> at com.sleepycat.je.txn.LockManager.newLockTimeoutException(
> LockManager.java:664)
>
> at com.sleepycat.je.txn.LockManager.makeTimeoutMsgInternal(
> LockManager.java:623)
>
> at com.sleepycat.je.txn.SyncedLockManager.makeTimeoutMsg(
> SyncedLockManager.java:97)
>
>
>
> I am not able to generate lineage due to this issue.
>
>
>
> Thanks!
>
>
>
> On Fri, Aug 4, 2017 at 5:05 PM, Vineet Mishra <clearmido...@gmail.com>
> wrote:
>
> Hi Team,
>
>
>
> I am using Atlas 0.8 release branch with hive 2.1 which works fine with
> hive import and with simple CTAS on hive but as when I give CTAS with some
> joins, its start failing to create lineage(the metadata still is captured
> by atlas)
>
>
>
> Also when I am running the same stuff with hive 1.1.0 it doesn't even get
> the metadata in the latter case, looks like there some persistence issue as
> what logs depicts. Has any one been through this situation?
>
>
>
> Atlas log with hive 2.1
>
> ---
>
> 2017-08-03 05:31:24,011 ERROR - [NotificationHookConsumer thread-0:] ~
> Could not commit transaction [71] due to storage exception in commit
> (StandardTitanGraph:673)
>
> com.thinkaurelius.titan.core.TitanException: Could not execute operation
> due to backend exception
>
> at com.thinkaurelius.titan.diskstorage.util.
> BackendOperation.execute(BackendOperation.java:44)
>
> at com.thinkaurelius.titan.diskstorage.keycolumnvalue.
> cache.CacheTransaction.persist(CacheTransaction.java:86)
>
> at com.thinkaurelius.titan.diskstorage.keycolumnvalue.
> cache.CacheTransaction.flushInternal(CacheTransaction.java:140)
>
> .
>
> .
>
> .
>
> .
>
> Caused by: com.thinkaurelius.titan.diskstorage.PermanentBackendException:
> Permanent failure in storage backend
>
> at com.thinkaurelius.titan.diskstorage.berkeleyje.
> BerkeleyJEKeyValueStore.insert(BerkeleyJEKeyValueStore.java:206)
>
>  .
>
> .
>
> .
>
> .
>
> Caused by: com.sleepycat.je.LockTimeoutException: (JE 5.0.73) Lock
> expired. Locker 2046519996 19950_NotificationHookConsumer thread-0_Txn:
> waited for lock on database=edgestore LockAddr:2100569783 LSN=0x0/0xeb475
> type=WRITE grant=WAIT_PROMOTION timeoutMillis=500 startTime=1501738283510
> endTime=1501738284010
>
> Owners: [ type="READ"/>,  type="READ"/>, ]
>
> Waiters: []
>
> Transaction 2046519996 19950_NotificationHookConsumer thread-0_Txn owns
> LockAddr:2100569783 
>
> Transaction 2046519996 19950_NotificationHookConsumer thread-0_Txn waits
> for LockAddr:2100569783
>
>
>
>
>
> Atlas log With hive 1.1
>
> --
>
> 2017-08-04 11:19:15,533 ERROR - [Thread-10:] ~ Evicted [2@7f00010114224-
> or1010051029126-corp-adobe-com1] from cache but waiting too long for
> transactions to close. Stale transaction alert on: [standardtitantx[null]]
> (ManagementLogger$SendAckOnTxClose:189)
>
> 2017-08-04 11:19:15,537 ERROR - [Thread-11:] ~ Evicted [3@7f00010114224-
> or1010051029126-corp-adobe-com1] from cache but waiting too long for
> transactions to close. Stale transaction alert on: [standardtitantx[null]]
> (ManagementLogger$SendAckOnTxClose:189)
>
>
>
>
>
> Any help would be highly appreciated.
>
>
>
> Thanks!
>
>
>


Re: Atlas not working for complex hive query on single node

2017-08-09 Thread Vineet Mishra
Hi Guys,

Any update on this?

Caused by: com.sleepycat.je.LockTimeoutException: (JE 5.0.73) Lock expired.
Locker 768997492 3544_NotificationHookConsumer thread-0_Txn: waited for
lock on database=edgestore LockAddr:1860143233 LSN=0x0/0xc8613 type=WRITE
grant=WAIT_PROMOTION timeoutMillis=500 startTime=1502275039421
endTime=1502275039921
Owners: [, ]
Waiters: []
Transaction 768997492 3544_NotificationHookConsumer thread-0_Txn owns
LockAddr:1860143233 
Transaction 768997492 3544_NotificationHookConsumer thread-0_Txn waits for
LockAddr:1860143233

at
com.sleepycat.je.txn.LockManager.newLockTimeoutException(LockManager.java:664)
at
com.sleepycat.je.txn.LockManager.makeTimeoutMsgInternal(LockManager.java:623)
at
com.sleepycat.je.txn.SyncedLockManager.makeTimeoutMsg(SyncedLockManager.java:97)

I am not able to generate lineage due to this issue.

Thanks!

On Fri, Aug 4, 2017 at 5:05 PM, Vineet Mishra <clearmido...@gmail.com>
wrote:

> Hi Team,
>
> I am using Atlas 0.8 release branch with hive 2.1 which works fine with
> hive import and with simple CTAS on hive but as when I give CTAS with some
> joins, its start failing to create lineage(the metadata still is captured
> by atlas)
>
> Also when I am running the same stuff with hive 1.1.0 it doesn't even get
> the metadata in the latter case, looks like there some persistence issue as
> what logs depicts. Has any one been through this situation?
>
> Atlas log with hive 2.1
> ---
> 2017-08-03 05:31:24,011 ERROR - [NotificationHookConsumer thread-0:] ~
> Could not commit transaction [71] due to storage exception in commit
> (StandardTitanGraph:673)
> com.thinkaurelius.titan.core.TitanException: Could not execute operation
> due to backend exception
> at com.thinkaurelius.titan.diskstorage.util.
> BackendOperation.execute(BackendOperation.java:44)
> at com.thinkaurelius.titan.diskstorage.keycolumnvalue.
> cache.CacheTransaction.persist(CacheTransaction.java:86)
> at com.thinkaurelius.titan.diskstorage.keycolumnvalue.
> cache.CacheTransaction.flushInternal(CacheTransaction.java:140)
> .
> .
> .
> .
> Caused by: com.thinkaurelius.titan.diskstorage.PermanentBackendException:
> Permanent failure in storage backend
> at com.thinkaurelius.titan.diskstorage.berkeleyje.
> BerkeleyJEKeyValueStore.insert(BerkeleyJEKeyValueStore.java:206)
>  .
> .
> .
> .
> Caused by: com.sleepycat.je.LockTimeoutException: (JE 5.0.73) Lock
> expired. Locker 2046519996 19950_NotificationHookConsumer thread-0_Txn:
> waited for lock on database=edgestore LockAddr:2100569783 LSN=0x0/0xeb475
> type=WRITE grant=WAIT_PROMOTION timeoutMillis=500 startTime=1501738283510
> endTime=1501738284010
> Owners: [ type="READ"/>,  type="READ"/>, ]
> Waiters: []
> Transaction 2046519996 19950_NotificationHookConsumer thread-0_Txn owns
> LockAddr:2100569783 
> Transaction 2046519996 19950_NotificationHookConsumer thread-0_Txn waits
> for LockAddr:2100569783
>
>
> Atlas log With hive 1.1
> --
> 2017-08-04 11:19:15,533 ERROR - [Thread-10:] ~ Evicted [2@7f00010114224-
> or1010051029126-corp-adobe-com1] from cache but waiting too long for
> transactions to close. Stale transaction alert on: [standardtitantx[null]]
> (ManagementLogger$SendAckOnTxClose:189)
> 2017-08-04 11:19:15,537 ERROR - [Thread-11:] ~ Evicted [3@7f00010114224-
> or1010051029126-corp-adobe-com1] from cache but waiting too long for
> transactions to close. Stale transaction alert on: [standardtitantx[null]]
> (ManagementLogger$SendAckOnTxClose:189)
>
>
> Any help would be highly appreciated.
>
> Thanks!
>