[SOLVED] Meteor 3.0 and Redis

UPDATE: I was wrong. I use graphql-redis-subscriptions npm package.

===========================================================
I tried to run a Meteor 3.0 but without MONGO_OPLOG_URL env
I saw Meteor was trying to connect to redis server at 127.0.0.1:6379

Error: connect ECONNREFUSED 127.0.0.1:6379
     at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1595:16)
     at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17) {
   errno: -111,
   code: 'ECONNREFUSED',
   syscall: 'connect',
   address: '127.0.0.1',
   port: 6379
 }

What do I need to make it use redis?

Can you expound on the issue:

Is there a confirmed Redis instance running on the mentioned port? Is this a question on how to connect to a redis server in general or is this a specific problem encountered with Meteor 3.0? Is the problem about setting up redis, connecting to redis, or Meteor 3.0 specific?

Hi, these are packages I’m using:

meteor-base@1.5.2-beta300.6             # Packages every Meteor app needs to have
mobile-experience@1.1.1-beta300.6       # Packages for a great mobile UX
mongo@2.0.0-beta300.6                   # The database Meteor supports right now
reactive-var@1.0.13-beta300.6            # Reactive variable for tracker

standard-minifier-css@1.9.3-beta300.6   # CSS minifier run for production mode
standard-minifier-js@3.0.0-beta300.6    # JS minifier run for production mode
es5-shim@4.8.1-beta300.6                # ECMAScript 5 compatibility for older browsers
ecmascript@0.16.8-beta300.6              # Enable ECMAScript2015+ syntax in app code
typescript@5.3.3-beta300.6              # Enable TypeScript syntax in .ts and .tsx modules
shell-server@0.6.0-beta300.6            # Server-side component of the `meteor shell` command
hot-module-replacement@0.5.4-beta300.6  # Update client in development without reloading the page

static-html@1.3.3-beta300.6             # Define static page content in .html files
accounts-base@3.0.0-beta300.6
accounts-password@3.0.0-beta300.6
server-render@0.4.2-beta300.6
zodern:types
aldeed:collection2@4.0.0-beta.7
tmeasday:check-npm-versions
meteortesting:mocha@3.1.0-beta300.0
react-meteor-data@3.0.0-beta300.1
minhna:connection-status-react

You can see there isn’t any package related to redis. I wonder why Meteor server is trying to connect to redis server (I’m not sure 100% but the port 6379 is the redis default port).
Do you think Meteor 3 brings Redis Oplog to the core?

Can you replicate with a new app using Meteor 3?

Although I support bringing redis-oplog to core, I will be very surprised if effort is being done now instead of after completing Meteor 3.0

I was wrong. My app uses graphql-redis-subscriptions npm package.