>> Log4J in Twitter4j doesn't initialize properly.

Can you explain that a little bit more?
What exceptions do you hit, "class not found", or sth. else?
Thx!

On Fri, Oct 14, 2016 at 2:20 PM, Wail Alkowaileet (JIRA) <j...@apache.org>
wrote:

>
>     [ https://issues.apache.org/jira/browse/ASTERIXDB-1694?
> page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&
> focusedCommentId=15576516#comment-15576516 ]
>
> Wail Alkowaileet commented on ASTERIXDB-1694:
> ---------------------------------------------
>
> After a long meeting, Mingda and I located the problem. Log4J in Twitter4j
> doesn't initialize properly.
> I don't know why that's the case. I suspect that there's something wrong
> in the deployment of AsterixDB.
>
> > Fail running Tweet Feed on Cluster of 16 nodes (while succeed on 4 nodes)
> > ------------------------------------------------------------
> -------------
> >
> >                 Key: ASTERIXDB-1694
> >                 URL: https://issues.apache.org/
> jira/browse/ASTERIXDB-1694
> >             Project: Apache AsterixDB
> >          Issue Type: Bug
> >          Components: Feeds
> >         Environment: asterix-server-0.8.9-SNAPSHOT-binary-assembly run
> on cluster
> >            Reporter: Mingda Li
> >            Assignee: Xikui Wang
> >   Original Estimate: 24h
> >  Remaining Estimate: 24h
> >
> > Recently, I am trying to run the data feed query on a cluster of 16
> nodes. All the query run well without error. But each time after I
> disconnect the feed, there is none of tweet data stored in dataverse.
> However, when I try to run other AQL queries, the cluster can work well.
> And I have ever used 4 nodes cluster to load Tweet data successfully. I
> also checked the log file and find no error there. This is wired. Does
> anyone know why? Has anyone ever used the data feed function on a cluster
> of 16 nodes or more?
> > I am using a asterix-server-0.8.9-SNAPSHOT-binary-assembly to configure
> cluster compiled by myself.
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.3.4#6332)
>

Reply via email to