The ListAzureBlobStorage was working fine with setting: .
Until it failed with the below error without anything being changed. I have restarted the nifi and reset all the properties again. However, the error still remains. I have looked into the similar questions: Link 1, Link 2, they do not provide solution to my specific problem.
ListAzureBlobStorage[id=34c1ea1d-0186-1000-aad1-11c9a28c4c83] Failed to properly initialize Processor. If still scheduled to run, NiFi will attempt to initialize and run the Processor again after the 'Administrative Yield Duration' has elapsed. Failure is due to java.io.IOException: Failed to obtain value from ZooKeeper for component with ID 34c1ea1d-0186-1000-aad1-11c9a28c4c83 with exception code CONNECTIONLOSS: org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode = ConnectionLoss for /nifi/components/34c1ea1d-0186-1000-aad1-11c9a28c4c83
↳ causes: java.io.IOException: Failed to obtain value from ZooKeeper for component with ID 34c1ea1d-0186-1000-aad1-11c9a28c4c83 with exception code CONNECTIONLOSS
I appreciate any help and direction to resolve this issue.
In the above case, nifi was set up using docker. Restarting the zookeeper container helped to resolve this issue.
Related
We have been running the Java QPID broker on CentOS for several years without issues when one of our production brokers failed and does not seem to be working properly after multiple restarts. This error continues to occur:
Caused by: org.apache.qpid.AMQStoreException: Error writing enqueued message with id 5836 for queue Ingest.instrument_particles with id 716760ac-c686-3454-b645-c86f15e29877 to database [error code 541: internal error]
at org.apache.qpid.server.store.derby.DerbyMessageStore.enqueueMessage(DerbyMessageStore.java:1242)
at org.apache.qpid.server.store.derby.DerbyMessageStore$DerbyTransaction.enqueueMessage(DerbyMessageStore.java:1989)
at org.apache.qpid.server.txn.AsyncAutoCommitTransaction.enqueue(AsyncAutoCommitTransaction.java:265)
... 12 more
Caused by: java.sql.SQLException: An unexpected exception was thrown
There's more to this stack trace, but the gist of it seems to be that QPID is failing to write to the message store. Is there a maximum size of files within the store? One of them exceeds 410GB. We are running JDK 1.8.0_332 on CentOS 7.9, if that makes a difference.
In a mapper activity I have passed the encoded data to tib:base64-to-string but while running it, getting the initialization error as follows.
ERROR [Job_Executor0] com.tibco.thor.frwk.Application -
TIBCO-THOR-FRWK-600026: Failed to start BW Application
[ServiceNow.v1.0.application:1.0]. Reason: TIBCO-BW-FRWK-600053:
Failed to initialize BW Component [ComponentAssyst_Attachment].
com.tibco.bw.core.runtime.api.BWEngineException:
TIBCO-BW-CORE-500232: Failed to initialize BW Component
[ServiceNow_Attachment], Application [ServiceNow.v1.0.application:1.0]
due to activity initialization error.
com.tibco.bw.core.runtime.ActivityInitException: TIBCO-BW-CORE-500618:
Failed to initialize the activity [TransformXml] in process
[ServiceNow.v1.0.ServiceNow_Attachment], module [ServiceNow.v1.0] due
to unexpected activity lifecycle error.
java.lang.AssertionError: resolver cannot be null.
23:22:36.900 INFO [Job_Executor0] com.tibco.thor.frwk.Application -
TIBCO-THOR-FRWK-300008: Stopped BW Application
[ServiceNow.v1.0.application:1.0]
can anyone help me on this to resolve this on priority.
i don't think it's because you mapped the encoded data in tib:base64-to-string, it seems more like an error due the version, try to increment the version and all the modules must have the same version.
I have a Talend Big Data job where I am trying to connect to Hive and create a table. Hive connect works fine. But tHiveCreate table gives the below exception.
Exception in component tHiveCreateTable_1 (Test)
org.apache.hive.service.cli.HiveSQLException: Error while processing statement: Cannot modify mapred.job.name at runtime. It is not in list of params that are allowed to be modified at runtime
at org.apache.hive.jdbc.Utils.verifySuccess(Utils.java:258)
at org.apache.hive.jdbc.Utils.verifySuccessWithInfo(Utils.java:244)
at org.apache.hive.jdbc.HiveStatement.execute(HiveStatement.java:247)
at local_project.test_0_1.Test.tHiveCreateTable_1Process(Test.java:643)
at local_project.test_0_1.Test.tHiveConnection_1Process(Test.java:498)
at local_project.test_0_1.Test.runJobInTOS(Test.java:948)
at local_project.test_0_1.Test.main(Test.java:799)
Caused by: org.apache.hive.service.cli.HiveSQLException: Error while processing statement: Cannot modify mapred.job.name at runtime. It is not in list of params that are allowed to be modified at runtime
at org.apache.hive.service.cli.operation.Operation.toSQLException(Operation.java:324)
at org.apache.hive.service.cli.operation.HiveCommandOperation.runInternal(HiveCommandOperation.java:108)
at org.apache.hive.service.cli.operation.Operation.run(Operation.java:264)
at org.apache.hive.service.cli.session.HiveSessionImpl.executeStatementInternal(HiveSessionImpl.java:479)
at org.apache.hive.service.cli.session.HiveSessionImpl.executeStatementAsync(HiveSessionImpl.java:466)
at org.apache.hive.service.cli.CLIService.executeStatementAsync(CLIService.java:315)
at org.apache.hive.service.cli.thrift.ThriftCLIService.ExecuteStatement(ThriftCLIService.java:509)
at org.apache.hive.service.cli.thrift.TCLIService$Processor$ExecuteStatement.getResult(TCLIService.java:1377)
at org.apache.hive.service.cli.thrift.TCLIService$Processor$ExecuteStatement.getResult(TCLIService.java:1362)
at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:39)
at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:39)
at org.apache.hive.service.auth.TSetIpAddressProcessor.process(TSetIpAddressProcessor.java:56)
at org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:286)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Earlier, the tHiveConnection was failing with same error. As per one of the older posts, I unchecked the Hadoop propeties from the tHiveConnect component and it worked fine. The similar properties are not available in the tHiveCreateTable component as I am using the tHiveConnection to provide connection details to tHiveCreateTable component.
Any help will be appreciated. Thanks
Anil
Similar problem as Talend (7.0.1) - Cannot modify mapred.job.name at runtime. Try to fix property hive.security.authorization.sqlstd.confwhitelist
I was able to fix the issue.
Added a property to custom hive site in Ambari as:
hive.security.authorization.sqlstd.confwhitelist.append with values
mapred.job.name|mapred.child.env|query.invoker|hive.query.name
The issue got fixed.
I am thus far unable to successfully run cassandra. I have arrived at a point in my efforts where I believe it is more efficient to reach out for help.
Installation method: datastax-ddc-64bit-3.9.0.msi
OS: Windows 7
Symptoms:
cmd> net start DataStax-DDC-Server
results in cmd output 'service is starting' and 'service was started successfully'.
datastax_ddc_server-stdout.log has this subsequent output, that is likely relevant:
WARN 10:38:17 Seed provider couldn't lookup host *myIPaddress*
Exception (org.apache.cassandra.exceptions.ConfigurationException) encountered during startup: The seed provider lists no seeds.
ERROR 10:38:17 Exception encountered during startup: The seed provider lists no seeds.
$
cmd> nodetool status
results in the following error message:
Error: Failed to connect to ‘127.0.0.1:7199’: Connection refused
I would also like to note that the Cassandra CQL Shell closes immediately after I open it.. I think that it quickly flashes an error similar to above.
Please be patient with me if I have included some useless information or am not approaching my issue from the correct perspective. I have not worked with apache cassandra before, nor have I configured a machine to facilitate an installation of any database engine.
Any help/insight is much appreciated,
Thanks!
I am running a Jmeter script in version 2.8. After running script in result
tree i am getting below mentioned error. But this error is not coming to
any specific request. I am getting this error for any random request. If i
ran test 1st time i am getting error for one png request. In next run same
png request passed successfully and error is seen for some different
request.
Can someone please help me to resolve this issue?
java.net.SocketException: Connection reset at
java.net.SocketInputStream.read(SocketInputStream.java:168) at
java.io.BufferedInputStream.fill(BufferedInputStream.java:218) at
java.io.BufferedInputStream.read1(BufferedInputStream.java:258) at
java.io.BufferedInputStream.read(BufferedInputStream.java:317) at
sun.net.www.MeteredStream.read(MeteredStream.java:116) at
java.io.FilterInputStream.read(FilterInputStream.java:116) at
sun.net.www.protocol.http.HttpURLConnection$HttpInputStream.read(HttpURLConnection.java:2676)
at org.apache.commons.io.input.ProxyInputStream.read(ProxyInputStream.java:99)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:256) at
java.io.BufferedInputStream.read(BufferedInputStream.java:317) at
java.io.FilterInputStream.read(FilterInputStream.java:90) at
org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.readResponse(HTTPSamplerBase.java:1620)
at org.apache.jmeter.protocol.http.sampler.HTTPAbstractImpl.readResponse(HTTPAbstractImpl.java:236)
at org.apache.jmeter.protocol.http.sampler.HTTPJavaImpl.readResponse(HTTPJavaImpl.java:282)
at org.apache.jmeter.protocol.http.sampler.HTTPJavaImpl.sample(HTTPJavaImpl.java:512)
at org.apache.jmeter.protocol.http.sampler.HTTPSamplerProxy.sample(HTTPSamplerProxy.java:62)
at org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:1054)
at org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:1043)
at org.apache.jmeter.threads.JMeterThread.process_sampler(JMeterThread.java:416)
at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:271)
at java.lang.Thread.run(Thread.java:662)
This reflects server side issues as you are getting connection reset error.
If you are doing real load test, do it in NON GUI mode, GUI mode is for scripting.