HBase PeriodicMemstoreFlusher exception - exception

I run HBase cluster and see in the log file every 10 seconds this exception:
2015-12-30 20:18:10,160 ERROR org.apache.hadoop.hbase.regionserver.HRegionServer$PeriodicMemstoreFlusher: Caught exception java.util.NoSuchElementException
at java.util.concurrent.ConcurrentHashMap$ValueIterator.next(ConcurrentHashMap.java:3436)
at java.util.Collections.min(Collections.java:596)
at org.apache.hadoop.hbase.regionserver.HRegion.getEarliestFlushTimeForAllStores(HRegion.java:1572)
at org.apache.hadoop.hbase.regionserver.HRegion.shouldFlush(HRegion.java:1904)
at org.apache.hadoop.hbase.regionserver.HRegionServer$PeriodicMemstoreFlusher.chore(HRegionServer.java:1509)
at org.apache.hadoop.hbase.Chore.run(Chore.java:87)
at java.lang.Thread.run(Thread.java:745)
Maybe someone knows what does it mean?
Looks like HBase bug.
Can you point me to the bug fix?
HBase version is 1.0.0-cdh5.4.8
thanks.

PeriodicMemstoreFlusher will run into the following exception. lastStoreFlushTimeMap is populated for families, if there is no family in the table or there is no entry in lastStoreFlushTimeMap.
Hope this helps!!

Related

Magento 2 : Exception #0 (Exception): Recoverable Error:

I have moved one magento 2 website from one server to another, after configuration, I got below error on category pages:
1 exception(s):
Exception #0 (Exception): Recoverable Error: Argument 1 passed to Mageplaza\Core\Helper\AbstractData::__construct() must be an instance of Magento\Framework\App\Helper\Context, instance of Magento\Framework\ObjectManager\ObjectManager given, called in /SOME_PATH/vendor/magento/framework/ObjectManager/Factory/AbstractFactory.php on line 93 and defined in /SOME_PATH/app/code/Mageplaza/Core/Helper/AbstractData.php on line 56
Exception #0 (Exception): Recoverable Error: Argument 1 passed to Mageplaza\Core\Helper\AbstractData::__construct() must be an instance of Magento\Framework\App\Helper\Context, instance of Magento\Framework\ObjectManager\ObjectManager given, called in /SOME_PATH/vendor/magento/framework/ObjectManager/Factory/AbstractFactory.php on line 93 and defined in /SOME_PATH/app/code/Mageplaza/Core/Helper/AbstractData.php on line 56
I have tried below things to resolve above:
Reindexing
Re-save category pages from backend
Created new category, and found its page working fine.
It seems there is a problem with database where old category urls need to be reindexed/rewritten or processed some way.
Can anyone help me to resolve this or any guide how I can troubleshoot this further?
Any help is appreciated!
Thanks
Deleting var/di directory resolves the problem. I didn't need to run any CLI command nor I need to do any cache clear stuff!

Neo4j-import fails

I'm trying to import a dataset using neo4j-import. Unfortunately the import fails with the following error message which is not saying much to me. Does anyone has an idea?
Thank you
The command was:
./neo4j-import --into /home_expes/dd77474h/neo4j-community-3.0.7/data/databases/graph.db/ --nodes /home_expes/dd77474h/Indexing-server/reduced_dbpedia_nodes.csv --relationships /home_expes/dd77474h/Indexing-server/reduced_dbpedia_relations.csv --stacktrace true --id-type
reduced_dbpedia_nodes.csv:
id:ID,uri,:LABEL
7,"http://dbpedia.org/resource/Albedo",Resource
reduced_dbpedia_relations.csv
:START_ID,:END_ID,:TYPE
1,2,"http://www.w3.org/1999/02/22-rdf-syntax-ns#type"
Error message:
Relationship --> Relationship Sparse
[>:231.50 MB/s--------------------------|LINK(3)==|*v:130.76 MB/s-----------------------------] 171M
Done in 24s 824ms
Minority relationships
[*INSERT--------------------------------------------------------------------------------------] 540K
Done in 14m 31s 126ms
Count groups
[*>:??----------------------------------------------------------------------------|COUNT------]12.2M
Done in 2s 786ms
Gather
java.lang.RuntimeException: Panic called, so exiting
at org.neo4j.unsafe.impl.batchimport.staging.AbstractStep.assertHealthy(AbstractStep.java:155)
at org.neo4j.unsafe.impl.batchimport.staging.ProducerStep.process(ProducerStep.java:84)
at org.neo4j.unsafe.impl.batchimport.staging.ProducerStep$1.run(ProducerStep.java:54)
Caused by: java.lang.IllegalStateException: There's no room for me for startIndex:28899 with a group count of -25966. This means that there's an asymmetry between calls to incrementGroupCount and actual contents sent into put
at org.neo4j.unsafe.impl.batchimport.RelationshipGroupCache.scanForFreeFrom(RelationshipGroupCache.java:203)
at org.neo4j.unsafe.impl.batchimport.RelationshipGroupCache.put(RelationshipGroupCache.java:159)
at org.neo4j.unsafe.impl.batchimport.CacheGroupsStep.process(CacheGroupsStep.java:48)
at org.neo4j.unsafe.impl.batchimport.CacheGroupsStep.process(CacheGroupsStep.java:31)
at org.neo4j.unsafe.impl.batchimport.staging.ProcessorStep.lambda$receive$2(ProcessorStep.java:97)
at org.neo4j.unsafe.impl.batchimport.executor.DynamicTaskExecutor$Processor.run(DynamicTaskExecutor.java:243)
Import error: Panic called, so exiting
Caused by:Panic called, so exiting
java.lang.RuntimeException: Panic called, so exiting
at org.neo4j.unsafe.impl.batchimport.staging.AbstractStep.assertHealthy(AbstractStep.java:155)
at org.neo4j.unsafe.impl.batchimport.staging.ProducerStep.process(ProducerStep.java:84)
at org.neo4j.unsafe.impl.batchimport.staging.ProducerStep$1.run(ProducerStep.java:54)
Caused by: java.lang.IllegalStateException: There's no room for me for startIndex:28899 with a group count of -25966. This means that there's an asymmetry between calls to incrementGroupCount and actual contents sent into put
at org.neo4j.unsafe.impl.batchimport.RelationshipGroupCache.scanForFreeFrom(RelationshipGroupCache.java:203)
at org.neo4j.unsafe.impl.batchimport.RelationshipGroupCache.put(RelationshipGroupCache.java:159)
at org.neo4j.unsafe.impl.batchimport.CacheGroupsStep.process(CacheGroupsStep.java:48)
at org.neo4j.unsafe.impl.batchimport.CacheGroupsStep.process(CacheGroupsStep.java:31)
at org.neo4j.unsafe.impl.batchimport.staging.ProcessorStep.lambda$receive$2(ProcessorStep.java:97)
at org.neo4j.unsafe.impl.batchimport.executor.DynamicTaskExecutor$Processor.run(DynamicTaskExecutor.java:243)
Thanks for your help, I found the bug. FYI see https://github.com/neo4j/neo4j/pull/8778 for fix.

Cause of boto3 error "An error occurred (Unavailable)...Tags could not be retrieved"?

I just started getting this error on a script that hasn't changed. Updating to boto3==1.4.3 had no effect. Doesn't look like throttling, does it? Not sure where to go with this one, any suggestions would be much appreciated.
File "/Library/Python/2.7/site-packages/botocore/client.py", line 251, in _api_call
return self._make_api_call(operation_name, kwargs)
File "/Library/Python/2.7/site-packages/botocore/client.py", line 537, in _make_api_call
raise ClientError(parsed_response, operation_name)
botocore.exceptions.ClientError: An error occurred (Unavailable)
when calling the DescribeSecurityGroups operation (reached max retries: 4):
Tags could not be retrieved.
Edited to add: As noted in comment below, this is coming from a seemingly innocuous call to describe_security_groups().
Another update: OK, this was transient and is no longer happening. Le sigh. Maybe some timeout due to network issues or something. I'll leave it up on SO for now, in case someone sees this and has a flash of insight.

Error while running phpunit test in yii framework

I just tried to run the unit test of the blog for the yii framework. But I got such error and i am not able to resolve the problem. Please feel free to share with me. Thank you in advance. And I got such error.
Do i need to set up the test database for the phpunit. If so how should i have to do it.
C:\wamp\www\yii\demos\blog\protected\tests>phpunit --verbose unit\CommentTest
C:\wamp\www\yii\demos\blog\protected\tests/../config/test.phpPHPUnit 3.6.10 by S
ebastian Bergmann.
Configuration read from C:\wamp\www\yii\demos\blog\protected\tests\phpunit.xml
EE
Time: 0 seconds, Memory: 7.75Mb
There were 2 errors:
1) CommentTest::testFindRecentComments
CDbException: The table "{{post}}" for active record class "Post" cannot be foun
d in the database.
C:\wamp\www\yii\framework\db\ar\CActiveRecord.php:2264
C:\wamp\www\yii\framework\db\ar\CActiveRecord.php:379
C:\wamp\www\yii\framework\test\CDbFixtureManager.php:301
C:\wamp\www\yii\framework\test\CDbTestCase.php:118
C:\wamp\bin\php\php5.3.9\phpunit:46
2) CommentTest::testApprove
CException: Table 'tbl_post' does not exist.
C:\wamp\www\yii\framework\test\CDbFixtureManager.php:254
C:\wamp\www\yii\framework\test\CDbFixtureManager.php:145
C:\wamp\www\yii\framework\test\CDbFixtureManager.php:305
C:\wamp\www\yii\framework\test\CDbTestCase.php:118
C:\wamp\bin\php\php5.3.9\phpunit:46
FAILURES!
Tests: 2, Assertions: 0, Errors: 2.
Acutally, I found the solution to this problem. It means that it doesn't find the table in the database. So, I executed this schema.mysql.sql file which was under the directory blog/protected/data. And everything worked fine –

Weird NPE on BatchingBatcher "JDBC driver did not return the expected number of row counts"

I'm running a spring/hibernate java app on tomcat and I'm seeing this funky error on update:
JDBC driver did not return the expected number of row counts
Caused by: java.lang.NullPointerException
at org.hibernate.jdbc.BatchingBatcher.checkRowCounts(BatchingBatcher.java:90)
at org.hibernate.jdbc.BatchingBatcher.doExecuteBatch(BatchingBatcher.java:70)
at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:268)
at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:262)
at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:179)
I recently updated my mysql connector to version 5.1.15.
Has anyone seen anything like this?
I think I encountered this once and fixed it by implementing hashCode and Equals methods for the object type returned by the query.