You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@usergrid.apache.org by Harish Singh Bisht <ha...@comprotechnologies.com> on 2015/10/20 11:55:07 UTC
Usergrid 2.0, Entity get automatically deleted from custom collection
Hello,
I have been evaluating usergrid (two-dot-o) branch and everything is mostly
great.
Ran into a problem with custom collections. It appears entities (custom
collections) get saved initially, but after sometime they're automatically
deleted? On further investigation of tomcat logs, I noted the following
errors/warning which matched with the deleted UUID
2015-09-17 11:17:22 ERROR
serialization.impl.MvccLogEntrySerializationStrategyImpl.parseColumn(447)<collectiontasks-1>-
DATA CORRUPTION DETECTED when de-serializing entity with Id
SimpleId{uuid=aa6efcaa-5d2d-11e5-b9f6-4dce0d97b002, type='product'} and
version aa7454cb-5d2d-11e5-8d3d-1271726ccb0d. This means the write was
truncated.
org.apache.usergrid.persistence.collection.exception.DataCorruptionException:
Unable to read entity data
2015-09-17 11:17:22 INFO
persistence.cassandra.DB.getAllColumns(390)<http-bio-8080-exec-2>-
getColumns cf=Entity_Dictionaries
key=aa6efcaa-5d2d-11e5-b9f6-4dce0d97b002:connected_types
2015-09-17 11:28:35 WARN
corepersistence.results.EntityVerifier.isValid(99)<http-bio-8080-exec-7>-
Entity uuid:aa6efcaa-5d2d-11e5-b9f6-4dce0d97b002 version
v:Optional.absent() is deleted but indexed, this is a bug
Can someone help me understand what might be going on?
Regards,
Harish
--
Regards,
Harish Singh Bisht
Re: Usergrid 2.0, Entity get automatically deleted from custom collection
Posted by Harish Singh Bisht <ha...@comprotechnologies.com>.
Hi Shawn,
Thanks for the reply.
I switched to the master branch, but ran into set-up / initialization
issues (i am trying a fresh installation). It seems things have changed
between the two-dot-o branch and current master and would appreciate some
help in resolving the following errors.
*My Setup is:*
Usergrid: master branch
Cassandra: 1.2.9
Elasticsearch: 1.4.2
Java: 1.8.0_60
*When starting tomcat I see the following error:*
2015-10-21 13:23:18 ERROR
cassandra.io.AbstractSearch.getQueueBounds(272)<JobSchedulerService
RUNNING>- Error getting oldest queue message ID
me.prettyprint.hector.api.exceptions.HInvalidRequestException:
InvalidRequestException(why:Keyspace 'Usergrid_Applications' does not exist)
*When i run /system/database/setup I get the following error:*
{"error":"uncaught","timestamp":1445435200484,"duration":0,"error_description":"Internal
Server
Error","exception":"org.apache.usergrid.rest.exceptions.UncaughtException","error_id":"2835c532-77fa-11e5-a8ed-12154b03f70b"}
*When i run /status i see the following.*
{
"timestamp" : 1445434379088,
"duration" : 3816,
"status" : {
"started" : 1445434352606,
"uptime" : 26505,
"version" : "2.1.1-SNAPSHOT",
* "cassandraAvailable" : true,*
* "cassandraStatus" : "RED",*
"managementAppIndexStatus" : "YELLOW",
"queueDepth" : 0,
"org.apache.usergrid.count.AbstractBatcher" : {
......
},
"org.apache.usergrid.count.CassandraSubmitter" : {
.....
}
}
}
Appreciate the help.
Thanks alot
Harish
On Tue, Oct 20, 2015 at 6:50 PM, Shawn Feldman <sh...@gmail.com>
wrote:
> You should use the master branch.
> On Tue, Oct 20, 2015 at 3:55 AM Harish Singh Bisht <
> harish.bisht@comprotechnologies.com> wrote:
>
>> Hello,
>>
>> I have been evaluating usergrid (two-dot-o) branch and everything is
>> mostly great.
>>
>> Ran into a problem with custom collections. It appears entities (custom
>> collections) get saved initially, but after sometime they're automatically
>> deleted? On further investigation of tomcat logs, I noted the following
>> errors/warning which matched with the deleted UUID
>>
>> 2015-09-17 11:17:22 ERROR
>> serialization.impl.MvccLogEntrySerializationStrategyImpl.parseColumn(447)<collectiontasks-1>-
>> DATA CORRUPTION DETECTED when de-serializing entity with Id
>> SimpleId{uuid=aa6efcaa-5d2d-11e5-b9f6-4dce0d97b002, type='product'} and
>> version aa7454cb-5d2d-11e5-8d3d-1271726ccb0d. This means the write was
>> truncated.
>> org.apache.usergrid.persistence.collection.exception.DataCorruptionException:
>> Unable to read entity data
>>
>> 2015-09-17 11:17:22 INFO
>> persistence.cassandra.DB.getAllColumns(390)<http-bio-8080-exec-2>-
>> getColumns cf=Entity_Dictionaries
>> key=aa6efcaa-5d2d-11e5-b9f6-4dce0d97b002:connected_types
>>
>> 2015-09-17 11:28:35 WARN
>> corepersistence.results.EntityVerifier.isValid(99)<http-bio-8080-exec-7>-
>> Entity uuid:aa6efcaa-5d2d-11e5-b9f6-4dce0d97b002 version
>> v:Optional.absent() is deleted but indexed, this is a bug
>>
>> Can someone help me understand what might be going on?
>>
>> Regards,
>> Harish
>>
>> --
>> Regards,
>> Harish Singh Bisht
>>
>>
--
Regards,
Harish Singh Bisht
Re: Usergrid 2.0, Entity get automatically deleted from custom collection
Posted by Harish Singh Bisht <ha...@comprotechnologies.com>.
Database Setup is working now.
Thank you very much Shawn!
On Tue, Oct 27, 2015 at 4:21 PM, Jaskaran Singh <ja...@gmail.com>
wrote:
> Thanks alot Shawn!
> Now my application is able to create the SQS and SNS clients on amazon.
> Appreciate all the help.
>
>
> On 24 October 2015 at 01:38, Shawn Feldman <sh...@gmail.com>
> wrote:
>
>> -DAWS_ACCESS_KEY_ID=someid -DAWS_SECRET_KEY=somekey
>>
>> On Fri, Oct 23, 2015 at 2:02 PM Jaskaran Singh <ja...@gmail.com>
>> wrote:
>>
>>> Hi Shawn,
>>>
>>> Thanks for your inputs. I am also facing an issue in the
>>> SNSQueueManagerImpl class. I found that the UsergridAwsCredentials class
>>> does find the aws credentials in the System class.
>>> Please advise where / how to set the amazon credentials for the SQS and
>>> SNS clients.
>>> Thank you very much for all the help.
>>>
>>> Thanks
>>> Jaskaran
>>>
>>> On 23 Oct 2015 22:23, "Shawn Feldman" <sh...@gmail.com> wrote:
>>>
>>>> make sure ES has the correct clustername, usergrid i think
>>>>
>>>> On Fri, Oct 23, 2015 at 10:52 AM Shawn Feldman <sh...@gmail.com>
>>>> wrote:
>>>>
>>>>> run PUT /system/database/setup
>>>>> run PUT /system/database/bootstrap
>>>>> run Get /system/superuser/setup
>>>>>
>>>>> On Fri, Oct 23, 2015 at 6:56 AM Harish Singh Bisht <
>>>>> harish.bisht@comprotechnologies.com> wrote:
>>>>>
>>>>>> HI Shawn,
>>>>>>
>>>>>> I was able to resolve the previous errors in the master branch. The
>>>>>> database had be to be setup using a PUT request, instead of a GET request
>>>>>> (as in Usergrid 1.0).
>>>>>>
>>>>>> However, now i am encountering an exception in the *SNSQueueManagerImpl
>>>>>> *class - it seems it creates Amazon SQS/SNS clients and is unable
>>>>>> to initialize the client libraries.
>>>>>> I also debugged the code and noted that *UsergridAwsCredentials *class
>>>>>> does 'not' find the amazon access key in the System class.
>>>>>>
>>>>>> I suspect, I'm missing certain properties in my
>>>>>> usergrid-deployment.properties file? Would appreciate if you point me in
>>>>>> the right direction please.
>>>>>>
>>>>>> Thanks in advance for your help
>>>>>> Harish
>>>>>> On Tue, Oct 20, 2015 at 6:50 PM, Shawn Feldman <
>>>>>> shawn.feldman@gmail.com> wrote:
>>>>>>
>>>>>>> You should use the master branch.
>>>>>>> On Tue, Oct 20, 2015 at 3:55 AM Harish Singh Bisht <
>>>>>>> harish.bisht@comprotechnologies.com> wrote:
>>>>>>>
>>>>>>>> Hello,
>>>>>>>>
>>>>>>>> I have been evaluating usergrid (two-dot-o) branch and everything
>>>>>>>> is mostly great.
>>>>>>>>
>>>>>>>> Ran into a problem with custom collections. It appears entities
>>>>>>>> (custom collections) get saved initially, but after sometime they're
>>>>>>>> automatically deleted? On further investigation of tomcat logs, I noted
>>>>>>>> the following errors/warning which matched with the deleted UUID
>>>>>>>>
>>>>>>>> 2015-09-17 11:17:22 ERROR
>>>>>>>> serialization.impl.MvccLogEntrySerializationStrategyImpl.parseColumn(447)<collectiontasks-1>-
>>>>>>>> DATA CORRUPTION DETECTED when de-serializing entity with Id
>>>>>>>> SimpleId{uuid=aa6efcaa-5d2d-11e5-b9f6-4dce0d97b002, type='product'} and
>>>>>>>> version aa7454cb-5d2d-11e5-8d3d-1271726ccb0d. This means the write was
>>>>>>>> truncated.
>>>>>>>> org.apache.usergrid.persistence.collection.exception.DataCorruptionException:
>>>>>>>> Unable to read entity data
>>>>>>>>
>>>>>>>> 2015-09-17 11:17:22 INFO
>>>>>>>> persistence.cassandra.DB.getAllColumns(390)<http-bio-8080-exec-2>-
>>>>>>>> getColumns cf=Entity_Dictionaries
>>>>>>>> key=aa6efcaa-5d2d-11e5-b9f6-4dce0d97b002:connected_types
>>>>>>>>
>>>>>>>> 2015-09-17 11:28:35 WARN
>>>>>>>> corepersistence.results.EntityVerifier.isValid(99)<http-bio-8080-exec-7>-
>>>>>>>> Entity uuid:aa6efcaa-5d2d-11e5-b9f6-4dce0d97b002 version
>>>>>>>> v:Optional.absent() is deleted but indexed, this is a bug
>>>>>>>>
>>>>>>>> Can someone help me understand what might be going on?
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>> Harish
>>>>>>>>
>>>>>>>> --
>>>>>>>> Regards,
>>>>>>>> Harish Singh Bisht
>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Regards,
>>>>>> Harish Singh Bisht
>>>>>>
>>>>>>
>
--
Regards,
Harish Singh Bisht
Re: Usergrid 2.0, Entity get automatically deleted from custom collection
Posted by Jaskaran Singh <ja...@gmail.com>.
Thanks alot Shawn!
Now my application is able to create the SQS and SNS clients on amazon.
Appreciate all the help.
On 24 October 2015 at 01:38, Shawn Feldman <sh...@gmail.com> wrote:
> -DAWS_ACCESS_KEY_ID=someid -DAWS_SECRET_KEY=somekey
>
> On Fri, Oct 23, 2015 at 2:02 PM Jaskaran Singh <ja...@gmail.com>
> wrote:
>
>> Hi Shawn,
>>
>> Thanks for your inputs. I am also facing an issue in the
>> SNSQueueManagerImpl class. I found that the UsergridAwsCredentials class
>> does find the aws credentials in the System class.
>> Please advise where / how to set the amazon credentials for the SQS and
>> SNS clients.
>> Thank you very much for all the help.
>>
>> Thanks
>> Jaskaran
>>
>> On 23 Oct 2015 22:23, "Shawn Feldman" <sh...@gmail.com> wrote:
>>
>>> make sure ES has the correct clustername, usergrid i think
>>>
>>> On Fri, Oct 23, 2015 at 10:52 AM Shawn Feldman <sh...@gmail.com>
>>> wrote:
>>>
>>>> run PUT /system/database/setup
>>>> run PUT /system/database/bootstrap
>>>> run Get /system/superuser/setup
>>>>
>>>> On Fri, Oct 23, 2015 at 6:56 AM Harish Singh Bisht <
>>>> harish.bisht@comprotechnologies.com> wrote:
>>>>
>>>>> HI Shawn,
>>>>>
>>>>> I was able to resolve the previous errors in the master branch. The
>>>>> database had be to be setup using a PUT request, instead of a GET request
>>>>> (as in Usergrid 1.0).
>>>>>
>>>>> However, now i am encountering an exception in the *SNSQueueManagerImpl
>>>>> *class - it seems it creates Amazon SQS/SNS clients and is unable
>>>>> to initialize the client libraries.
>>>>> I also debugged the code and noted that *UsergridAwsCredentials *class
>>>>> does 'not' find the amazon access key in the System class.
>>>>>
>>>>> I suspect, I'm missing certain properties in my
>>>>> usergrid-deployment.properties file? Would appreciate if you point me in
>>>>> the right direction please.
>>>>>
>>>>> Thanks in advance for your help
>>>>> Harish
>>>>> On Tue, Oct 20, 2015 at 6:50 PM, Shawn Feldman <
>>>>> shawn.feldman@gmail.com> wrote:
>>>>>
>>>>>> You should use the master branch.
>>>>>> On Tue, Oct 20, 2015 at 3:55 AM Harish Singh Bisht <
>>>>>> harish.bisht@comprotechnologies.com> wrote:
>>>>>>
>>>>>>> Hello,
>>>>>>>
>>>>>>> I have been evaluating usergrid (two-dot-o) branch and everything is
>>>>>>> mostly great.
>>>>>>>
>>>>>>> Ran into a problem with custom collections. It appears entities
>>>>>>> (custom collections) get saved initially, but after sometime they're
>>>>>>> automatically deleted? On further investigation of tomcat logs, I noted
>>>>>>> the following errors/warning which matched with the deleted UUID
>>>>>>>
>>>>>>> 2015-09-17 11:17:22 ERROR
>>>>>>> serialization.impl.MvccLogEntrySerializationStrategyImpl.parseColumn(447)<collectiontasks-1>-
>>>>>>> DATA CORRUPTION DETECTED when de-serializing entity with Id
>>>>>>> SimpleId{uuid=aa6efcaa-5d2d-11e5-b9f6-4dce0d97b002, type='product'} and
>>>>>>> version aa7454cb-5d2d-11e5-8d3d-1271726ccb0d. This means the write was
>>>>>>> truncated.
>>>>>>> org.apache.usergrid.persistence.collection.exception.DataCorruptionException:
>>>>>>> Unable to read entity data
>>>>>>>
>>>>>>> 2015-09-17 11:17:22 INFO
>>>>>>> persistence.cassandra.DB.getAllColumns(390)<http-bio-8080-exec-2>-
>>>>>>> getColumns cf=Entity_Dictionaries
>>>>>>> key=aa6efcaa-5d2d-11e5-b9f6-4dce0d97b002:connected_types
>>>>>>>
>>>>>>> 2015-09-17 11:28:35 WARN
>>>>>>> corepersistence.results.EntityVerifier.isValid(99)<http-bio-8080-exec-7>-
>>>>>>> Entity uuid:aa6efcaa-5d2d-11e5-b9f6-4dce0d97b002 version
>>>>>>> v:Optional.absent() is deleted but indexed, this is a bug
>>>>>>>
>>>>>>> Can someone help me understand what might be going on?
>>>>>>>
>>>>>>> Regards,
>>>>>>> Harish
>>>>>>>
>>>>>>> --
>>>>>>> Regards,
>>>>>>> Harish Singh Bisht
>>>>>>>
>>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Regards,
>>>>> Harish Singh Bisht
>>>>>
>>>>>
Re: Usergrid 2.0, Entity get automatically deleted from custom collection
Posted by Shawn Feldman <sh...@gmail.com>.
-DAWS_ACCESS_KEY_ID=someid -DAWS_SECRET_KEY=somekey
On Fri, Oct 23, 2015 at 2:02 PM Jaskaran Singh <ja...@gmail.com>
wrote:
> Hi Shawn,
>
> Thanks for your inputs. I am also facing an issue in the
> SNSQueueManagerImpl class. I found that the UsergridAwsCredentials class
> does find the aws credentials in the System class.
> Please advise where / how to set the amazon credentials for the SQS and
> SNS clients.
> Thank you very much for all the help.
>
> Thanks
> Jaskaran
>
> On 23 Oct 2015 22:23, "Shawn Feldman" <sh...@gmail.com> wrote:
>
>> make sure ES has the correct clustername, usergrid i think
>>
>> On Fri, Oct 23, 2015 at 10:52 AM Shawn Feldman <sh...@gmail.com>
>> wrote:
>>
>>> run PUT /system/database/setup
>>> run PUT /system/database/bootstrap
>>> run Get /system/superuser/setup
>>>
>>> On Fri, Oct 23, 2015 at 6:56 AM Harish Singh Bisht <
>>> harish.bisht@comprotechnologies.com> wrote:
>>>
>>>> HI Shawn,
>>>>
>>>> I was able to resolve the previous errors in the master branch. The
>>>> database had be to be setup using a PUT request, instead of a GET request
>>>> (as in Usergrid 1.0).
>>>>
>>>> However, now i am encountering an exception in the *SNSQueueManagerImpl
>>>> *class - it seems it creates Amazon SQS/SNS clients and is unable
>>>> to initialize the client libraries.
>>>> I also debugged the code and noted that *UsergridAwsCredentials *class
>>>> does 'not' find the amazon access key in the System class.
>>>>
>>>> I suspect, I'm missing certain properties in my
>>>> usergrid-deployment.properties file? Would appreciate if you point me in
>>>> the right direction please.
>>>>
>>>> Thanks in advance for your help
>>>> Harish
>>>> On Tue, Oct 20, 2015 at 6:50 PM, Shawn Feldman <shawn.feldman@gmail.com
>>>> > wrote:
>>>>
>>>>> You should use the master branch.
>>>>> On Tue, Oct 20, 2015 at 3:55 AM Harish Singh Bisht <
>>>>> harish.bisht@comprotechnologies.com> wrote:
>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> I have been evaluating usergrid (two-dot-o) branch and everything is
>>>>>> mostly great.
>>>>>>
>>>>>> Ran into a problem with custom collections. It appears entities
>>>>>> (custom collections) get saved initially, but after sometime they're
>>>>>> automatically deleted? On further investigation of tomcat logs, I noted
>>>>>> the following errors/warning which matched with the deleted UUID
>>>>>>
>>>>>> 2015-09-17 11:17:22 ERROR
>>>>>> serialization.impl.MvccLogEntrySerializationStrategyImpl.parseColumn(447)<collectiontasks-1>-
>>>>>> DATA CORRUPTION DETECTED when de-serializing entity with Id
>>>>>> SimpleId{uuid=aa6efcaa-5d2d-11e5-b9f6-4dce0d97b002, type='product'} and
>>>>>> version aa7454cb-5d2d-11e5-8d3d-1271726ccb0d. This means the write was
>>>>>> truncated.
>>>>>> org.apache.usergrid.persistence.collection.exception.DataCorruptionException:
>>>>>> Unable to read entity data
>>>>>>
>>>>>> 2015-09-17 11:17:22 INFO
>>>>>> persistence.cassandra.DB.getAllColumns(390)<http-bio-8080-exec-2>-
>>>>>> getColumns cf=Entity_Dictionaries
>>>>>> key=aa6efcaa-5d2d-11e5-b9f6-4dce0d97b002:connected_types
>>>>>>
>>>>>> 2015-09-17 11:28:35 WARN
>>>>>> corepersistence.results.EntityVerifier.isValid(99)<http-bio-8080-exec-7>-
>>>>>> Entity uuid:aa6efcaa-5d2d-11e5-b9f6-4dce0d97b002 version
>>>>>> v:Optional.absent() is deleted but indexed, this is a bug
>>>>>>
>>>>>> Can someone help me understand what might be going on?
>>>>>>
>>>>>> Regards,
>>>>>> Harish
>>>>>>
>>>>>> --
>>>>>> Regards,
>>>>>> Harish Singh Bisht
>>>>>>
>>>>>>
>>>>
>>>>
>>>> --
>>>> Regards,
>>>> Harish Singh Bisht
>>>>
>>>>
Re: Usergrid 2.0, Entity get automatically deleted from custom collection
Posted by Jaskaran Singh <ja...@gmail.com>.
Hi Shawn,
Thanks for your inputs. I am also facing an issue in the
SNSQueueManagerImpl class. I found that the UsergridAwsCredentials class
does find the aws credentials in the System class.
Please advise where / how to set the amazon credentials for the SQS and
SNS clients.
Thank you very much for all the help.
Thanks
Jaskaran
On 23 Oct 2015 22:23, "Shawn Feldman" <sh...@gmail.com> wrote:
> make sure ES has the correct clustername, usergrid i think
>
> On Fri, Oct 23, 2015 at 10:52 AM Shawn Feldman <sh...@gmail.com>
> wrote:
>
>> run PUT /system/database/setup
>> run PUT /system/database/bootstrap
>> run Get /system/superuser/setup
>>
>> On Fri, Oct 23, 2015 at 6:56 AM Harish Singh Bisht <
>> harish.bisht@comprotechnologies.com> wrote:
>>
>>> HI Shawn,
>>>
>>> I was able to resolve the previous errors in the master branch. The
>>> database had be to be setup using a PUT request, instead of a GET request
>>> (as in Usergrid 1.0).
>>>
>>> However, now i am encountering an exception in the *SNSQueueManagerImpl
>>> *class - it seems it creates Amazon SQS/SNS clients and is unable
>>> to initialize the client libraries.
>>> I also debugged the code and noted that *UsergridAwsCredentials *class
>>> does 'not' find the amazon access key in the System class.
>>>
>>> I suspect, I'm missing certain properties in my
>>> usergrid-deployment.properties file? Would appreciate if you point me in
>>> the right direction please.
>>>
>>> Thanks in advance for your help
>>> Harish
>>> On Tue, Oct 20, 2015 at 6:50 PM, Shawn Feldman <sh...@gmail.com>
>>> wrote:
>>>
>>>> You should use the master branch.
>>>> On Tue, Oct 20, 2015 at 3:55 AM Harish Singh Bisht <
>>>> harish.bisht@comprotechnologies.com> wrote:
>>>>
>>>>> Hello,
>>>>>
>>>>> I have been evaluating usergrid (two-dot-o) branch and everything is
>>>>> mostly great.
>>>>>
>>>>> Ran into a problem with custom collections. It appears entities
>>>>> (custom collections) get saved initially, but after sometime they're
>>>>> automatically deleted? On further investigation of tomcat logs, I noted
>>>>> the following errors/warning which matched with the deleted UUID
>>>>>
>>>>> 2015-09-17 11:17:22 ERROR
>>>>> serialization.impl.MvccLogEntrySerializationStrategyImpl.parseColumn(447)<collectiontasks-1>-
>>>>> DATA CORRUPTION DETECTED when de-serializing entity with Id
>>>>> SimpleId{uuid=aa6efcaa-5d2d-11e5-b9f6-4dce0d97b002, type='product'} and
>>>>> version aa7454cb-5d2d-11e5-8d3d-1271726ccb0d. This means the write was
>>>>> truncated.
>>>>> org.apache.usergrid.persistence.collection.exception.DataCorruptionException:
>>>>> Unable to read entity data
>>>>>
>>>>> 2015-09-17 11:17:22 INFO
>>>>> persistence.cassandra.DB.getAllColumns(390)<http-bio-8080-exec-2>-
>>>>> getColumns cf=Entity_Dictionaries
>>>>> key=aa6efcaa-5d2d-11e5-b9f6-4dce0d97b002:connected_types
>>>>>
>>>>> 2015-09-17 11:28:35 WARN
>>>>> corepersistence.results.EntityVerifier.isValid(99)<http-bio-8080-exec-7>-
>>>>> Entity uuid:aa6efcaa-5d2d-11e5-b9f6-4dce0d97b002 version
>>>>> v:Optional.absent() is deleted but indexed, this is a bug
>>>>>
>>>>> Can someone help me understand what might be going on?
>>>>>
>>>>> Regards,
>>>>> Harish
>>>>>
>>>>> --
>>>>> Regards,
>>>>> Harish Singh Bisht
>>>>>
>>>>>
>>>
>>>
>>> --
>>> Regards,
>>> Harish Singh Bisht
>>>
>>>
Re: Usergrid 2.0, Entity get automatically deleted from custom collection
Posted by Shawn Feldman <sh...@gmail.com>.
make sure ES has the correct clustername, usergrid i think
On Fri, Oct 23, 2015 at 10:52 AM Shawn Feldman <sh...@gmail.com>
wrote:
> run PUT /system/database/setup
> run PUT /system/database/bootstrap
> run Get /system/superuser/setup
>
> On Fri, Oct 23, 2015 at 6:56 AM Harish Singh Bisht <
> harish.bisht@comprotechnologies.com> wrote:
>
>> HI Shawn,
>>
>> I was able to resolve the previous errors in the master branch. The
>> database had be to be setup using a PUT request, instead of a GET request
>> (as in Usergrid 1.0).
>>
>> However, now i am encountering an exception in the *SNSQueueManagerImpl *class
>> - it seems it creates Amazon SQS/SNS clients and is unable
>> to initialize the client libraries.
>> I also debugged the code and noted that *UsergridAwsCredentials *class
>> does 'not' find the amazon access key in the System class.
>>
>> I suspect, I'm missing certain properties in my
>> usergrid-deployment.properties file? Would appreciate if you point me in
>> the right direction please.
>>
>> Thanks in advance for your help
>> Harish
>> On Tue, Oct 20, 2015 at 6:50 PM, Shawn Feldman <sh...@gmail.com>
>> wrote:
>>
>>> You should use the master branch.
>>> On Tue, Oct 20, 2015 at 3:55 AM Harish Singh Bisht <
>>> harish.bisht@comprotechnologies.com> wrote:
>>>
>>>> Hello,
>>>>
>>>> I have been evaluating usergrid (two-dot-o) branch and everything is
>>>> mostly great.
>>>>
>>>> Ran into a problem with custom collections. It appears entities (custom
>>>> collections) get saved initially, but after sometime they're automatically
>>>> deleted? On further investigation of tomcat logs, I noted the following
>>>> errors/warning which matched with the deleted UUID
>>>>
>>>> 2015-09-17 11:17:22 ERROR
>>>> serialization.impl.MvccLogEntrySerializationStrategyImpl.parseColumn(447)<collectiontasks-1>-
>>>> DATA CORRUPTION DETECTED when de-serializing entity with Id
>>>> SimpleId{uuid=aa6efcaa-5d2d-11e5-b9f6-4dce0d97b002, type='product'} and
>>>> version aa7454cb-5d2d-11e5-8d3d-1271726ccb0d. This means the write was
>>>> truncated.
>>>> org.apache.usergrid.persistence.collection.exception.DataCorruptionException:
>>>> Unable to read entity data
>>>>
>>>> 2015-09-17 11:17:22 INFO
>>>> persistence.cassandra.DB.getAllColumns(390)<http-bio-8080-exec-2>-
>>>> getColumns cf=Entity_Dictionaries
>>>> key=aa6efcaa-5d2d-11e5-b9f6-4dce0d97b002:connected_types
>>>>
>>>> 2015-09-17 11:28:35 WARN
>>>> corepersistence.results.EntityVerifier.isValid(99)<http-bio-8080-exec-7>-
>>>> Entity uuid:aa6efcaa-5d2d-11e5-b9f6-4dce0d97b002 version
>>>> v:Optional.absent() is deleted but indexed, this is a bug
>>>>
>>>> Can someone help me understand what might be going on?
>>>>
>>>> Regards,
>>>> Harish
>>>>
>>>> --
>>>> Regards,
>>>> Harish Singh Bisht
>>>>
>>>>
>>
>>
>> --
>> Regards,
>> Harish Singh Bisht
>>
>>
Re: Usergrid 2.0, Entity get automatically deleted from custom collection
Posted by Shawn Feldman <sh...@gmail.com>.
run PUT /system/database/setup
run PUT /system/database/bootstrap
run Get /system/superuser/setup
On Fri, Oct 23, 2015 at 6:56 AM Harish Singh Bisht <
harish.bisht@comprotechnologies.com> wrote:
> HI Shawn,
>
> I was able to resolve the previous errors in the master branch. The
> database had be to be setup using a PUT request, instead of a GET request
> (as in Usergrid 1.0).
>
> However, now i am encountering an exception in the *SNSQueueManagerImpl *class
> - it seems it creates Amazon SQS/SNS clients and is unable
> to initialize the client libraries.
> I also debugged the code and noted that *UsergridAwsCredentials *class
> does 'not' find the amazon access key in the System class.
>
> I suspect, I'm missing certain properties in my
> usergrid-deployment.properties file? Would appreciate if you point me in
> the right direction please.
>
> Thanks in advance for your help
> Harish
> On Tue, Oct 20, 2015 at 6:50 PM, Shawn Feldman <sh...@gmail.com>
> wrote:
>
>> You should use the master branch.
>> On Tue, Oct 20, 2015 at 3:55 AM Harish Singh Bisht <
>> harish.bisht@comprotechnologies.com> wrote:
>>
>>> Hello,
>>>
>>> I have been evaluating usergrid (two-dot-o) branch and everything is
>>> mostly great.
>>>
>>> Ran into a problem with custom collections. It appears entities (custom
>>> collections) get saved initially, but after sometime they're automatically
>>> deleted? On further investigation of tomcat logs, I noted the following
>>> errors/warning which matched with the deleted UUID
>>>
>>> 2015-09-17 11:17:22 ERROR
>>> serialization.impl.MvccLogEntrySerializationStrategyImpl.parseColumn(447)<collectiontasks-1>-
>>> DATA CORRUPTION DETECTED when de-serializing entity with Id
>>> SimpleId{uuid=aa6efcaa-5d2d-11e5-b9f6-4dce0d97b002, type='product'} and
>>> version aa7454cb-5d2d-11e5-8d3d-1271726ccb0d. This means the write was
>>> truncated.
>>> org.apache.usergrid.persistence.collection.exception.DataCorruptionException:
>>> Unable to read entity data
>>>
>>> 2015-09-17 11:17:22 INFO
>>> persistence.cassandra.DB.getAllColumns(390)<http-bio-8080-exec-2>-
>>> getColumns cf=Entity_Dictionaries
>>> key=aa6efcaa-5d2d-11e5-b9f6-4dce0d97b002:connected_types
>>>
>>> 2015-09-17 11:28:35 WARN
>>> corepersistence.results.EntityVerifier.isValid(99)<http-bio-8080-exec-7>-
>>> Entity uuid:aa6efcaa-5d2d-11e5-b9f6-4dce0d97b002 version
>>> v:Optional.absent() is deleted but indexed, this is a bug
>>>
>>> Can someone help me understand what might be going on?
>>>
>>> Regards,
>>> Harish
>>>
>>> --
>>> Regards,
>>> Harish Singh Bisht
>>>
>>>
>
>
> --
> Regards,
> Harish Singh Bisht
>
>
Re: Usergrid 2.0, Entity get automatically deleted from custom collection
Posted by Harish Singh Bisht <ha...@comprotechnologies.com>.
HI Shawn,
I was able to resolve the previous errors in the master branch. The
database had be to be setup using a PUT request, instead of a GET request
(as in Usergrid 1.0).
However, now i am encountering an exception in the *SNSQueueManagerImpl *class
- it seems it creates Amazon SQS/SNS clients and is unable
to initialize the client libraries.
I also debugged the code and noted that *UsergridAwsCredentials *class
does 'not' find the amazon access key in the System class.
I suspect, I'm missing certain properties in my
usergrid-deployment.properties file? Would appreciate if you point me in
the right direction please.
Thanks in advance for your help
Harish
On Tue, Oct 20, 2015 at 6:50 PM, Shawn Feldman <sh...@gmail.com>
wrote:
> You should use the master branch.
> On Tue, Oct 20, 2015 at 3:55 AM Harish Singh Bisht <
> harish.bisht@comprotechnologies.com> wrote:
>
>> Hello,
>>
>> I have been evaluating usergrid (two-dot-o) branch and everything is
>> mostly great.
>>
>> Ran into a problem with custom collections. It appears entities (custom
>> collections) get saved initially, but after sometime they're automatically
>> deleted? On further investigation of tomcat logs, I noted the following
>> errors/warning which matched with the deleted UUID
>>
>> 2015-09-17 11:17:22 ERROR
>> serialization.impl.MvccLogEntrySerializationStrategyImpl.parseColumn(447)<collectiontasks-1>-
>> DATA CORRUPTION DETECTED when de-serializing entity with Id
>> SimpleId{uuid=aa6efcaa-5d2d-11e5-b9f6-4dce0d97b002, type='product'} and
>> version aa7454cb-5d2d-11e5-8d3d-1271726ccb0d. This means the write was
>> truncated.
>> org.apache.usergrid.persistence.collection.exception.DataCorruptionException:
>> Unable to read entity data
>>
>> 2015-09-17 11:17:22 INFO
>> persistence.cassandra.DB.getAllColumns(390)<http-bio-8080-exec-2>-
>> getColumns cf=Entity_Dictionaries
>> key=aa6efcaa-5d2d-11e5-b9f6-4dce0d97b002:connected_types
>>
>> 2015-09-17 11:28:35 WARN
>> corepersistence.results.EntityVerifier.isValid(99)<http-bio-8080-exec-7>-
>> Entity uuid:aa6efcaa-5d2d-11e5-b9f6-4dce0d97b002 version
>> v:Optional.absent() is deleted but indexed, this is a bug
>>
>> Can someone help me understand what might be going on?
>>
>> Regards,
>> Harish
>>
>> --
>> Regards,
>> Harish Singh Bisht
>>
>>
--
Regards,
Harish Singh Bisht
Re: Usergrid 2.0, Entity get automatically deleted from custom collection
Posted by Shawn Feldman <sh...@gmail.com>.
You should use the master branch.
On Tue, Oct 20, 2015 at 3:55 AM Harish Singh Bisht <
harish.bisht@comprotechnologies.com> wrote:
> Hello,
>
> I have been evaluating usergrid (two-dot-o) branch and everything is
> mostly great.
>
> Ran into a problem with custom collections. It appears entities (custom
> collections) get saved initially, but after sometime they're automatically
> deleted? On further investigation of tomcat logs, I noted the following
> errors/warning which matched with the deleted UUID
>
> 2015-09-17 11:17:22 ERROR
> serialization.impl.MvccLogEntrySerializationStrategyImpl.parseColumn(447)<collectiontasks-1>-
> DATA CORRUPTION DETECTED when de-serializing entity with Id
> SimpleId{uuid=aa6efcaa-5d2d-11e5-b9f6-4dce0d97b002, type='product'} and
> version aa7454cb-5d2d-11e5-8d3d-1271726ccb0d. This means the write was
> truncated.
> org.apache.usergrid.persistence.collection.exception.DataCorruptionException:
> Unable to read entity data
>
> 2015-09-17 11:17:22 INFO
> persistence.cassandra.DB.getAllColumns(390)<http-bio-8080-exec-2>-
> getColumns cf=Entity_Dictionaries
> key=aa6efcaa-5d2d-11e5-b9f6-4dce0d97b002:connected_types
>
> 2015-09-17 11:28:35 WARN
> corepersistence.results.EntityVerifier.isValid(99)<http-bio-8080-exec-7>-
> Entity uuid:aa6efcaa-5d2d-11e5-b9f6-4dce0d97b002 version
> v:Optional.absent() is deleted but indexed, this is a bug
>
> Can someone help me understand what might be going on?
>
> Regards,
> Harish
>
> --
> Regards,
> Harish Singh Bisht
>
>